Exploration and Integration of File Systems in Llamaos

Total Page:16

File Type:pdf, Size:1020Kb

Exploration and Integration of File Systems in Llamaos Exploration and Integration of File Systems in LlamaOS A thesis submitted to the Division of Research and Advanced Studies of the University of Cincinnati in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in the School of Electrical and Computing Systems of the College of Engineering and Applied Science November 12, 2014 by Kyle Craig BS Computer Engineering, University of Cincinnati, 2013 Thesis Advisor and Committee Chair: Dr. Philip A. Wilsey Abstract LlamaOS is a minimalist and customizable operating system for Xen-based virtual machines running on parallel cluster hardware. With the addition of LlamaMPI, a custom implementation of the standard Message Passing Interface (MPI), LlamaOS is able to achieve significant performance gains for fine-grained parallel applications. However, the initial setup of LlamaOS lacked full file system support which limited its use to only a limited set of applications. Initially LlamaOS could only support a single read-only file for each instance in the parallel virtual machine. The original design of LlamaOS was motivated by work in parallel discrete-event simulation. However, the single-file file system of LlamaOS had significant drawbacks. For some simulation models, multiple configuration files are needed to fully run properly and to make these models run on LlamaOS the parallel simulator that was being evaluated had to be changed so that only a single configuration file was needed. This went against one of the base principles of LlamaOS: Outside applications can be run with little to no modification. Another major drawback was that the models could not create and write their own results file limiting the amount of data that could be gathered from running in LlamaOS. In order to alleviate these issues this thesis explores the implementation of a bare-bones Virtual File System (VFS) and, consequently, support for a Second Extended File System (Ext2) driver has been added to LlamaOS. In order to test the functionality and performance of the new LlamaOS file system, the bonnie benchmark (a common tool used for benchmarking various types of file I/O at a basic system level) was ported to run within LlamaOS. The benchmark showed promising results, and verified that the file system implementation was functional and able to perform file reads, file writes, and file creation. In addition to the bonnie bench- mark a couple of parallel simulation models were also used to verify that the file system implementation achieved its goal of efficiently supporting parallel simulation within LlamaOS with little to no modification i to the original simulation kernel. ii Acknowledgments I would like to thank my family for supporting me throughout this endeavour. I would like to thank Andrea Giovine for putting up with the late nights and aloof behavior I exhibited while working. I would like to thank Eric Carver and Josh Hay for being great friends that I was able to go through this experience together with. Finally, I would like to Dr. Wilsey for being a great advisor and for just putting up with me in general. Support for this work was provided in part by the National Science Foundation under grant CNS-0915337. iii Contents 1 Introduction 1 1.1 Motivation . 2 1.2 Thesis Overview . 3 2 Background 5 2.1 Virtualization . 5 2.2 Xen Hypervisor . 8 2.3 LlamaOS . 9 2.4 File Systems . 13 2.4.1 The Second Extended File System . 16 2.5 WARPED ............................................. 19 2.5.1 Discrete Event Simulation . 20 2.5.2 Parallel Discrete Event Simulation . 20 2.5.3 Time Warp Mechanism . 22 3 Related Work 24 3.1 The CROCOS Kernel . 24 3.2 Time Warp Operating System . 25 4 Overview of Approach 29 4.1 File System Choice . 29 4.1.1 The FAT File System . 30 iv CONTENTS 4.1.2 The MINIX File System . 32 4.1.3 Final Comparison . 34 4.2 File System Benchmark Research . 34 5 Implementation Details 37 5.1 File System . 37 5.1.1 Virtual File System . 37 5.1.2 Ext2 Driver . 40 5.2 Benchmark Modifications . 45 6 Performance Results 46 6.1 File System Benchmarks . 46 6.2 WARPED Tests . 49 7 Conclusion and Future Work 53 7.1 Summary . 53 7.2 Suggestions for Future Work . 53 7.2.1 LlamaOS . 54 7.2.2 File System Implementation . 54 v List of Figures 2.1 Type-1 Hypervisor ....................................... 6 2.2 Type-2 Hypervisor ....................................... 7 2.3 Comparison of Native and Virtual Linux to LlamaOS [29] . 11 2.4 LlamaNET block diagram [29] ................................ 12 2.5 I-node direct block mapping [19] ............................... 14 2.6 I-node indirect block mapping [19] .............................. 15 2.7 Virtual File System indirection [12] ............................. 17 2.8 Physical structure of the Ext2 file system .......................... 18 2.9 Translation of bitmap to disk blocks [7] ........................... 19 2.10 PDES Illustration [17] ..................................... 21 3.1 Structure of the Time Warp Operating System [23] .................... 26 4.1 Layout of the FAT12/16 File System [5] ........................... 31 4.2 Layout of the MINIX File System [41] ............................ 33 5.1 Flowchart of the fs open function. .............................. 39 6.1 Bar Chart Demonstrating Increase in Speed with File Size . 48 6.2 Comparison of Native and LlamaOS Simulation Times . 51 vi List of Tables 2.1 Xen para-virtualized x86 interface [8] ............................ 9 4.1 Comparison of FAT, MINIX, and Ext2 file systems ..................... 34 6.1 Test System Specifications ................................... 46 6.2 Averages of bonnie results by file size ............................ 47 6.3 Native bonnie results for test system ............................. 47 6.4 Comparison between LlamaOS and Native for epidemic model . 51 vii Chapter 1 Introduction In recent years significant improvements have been made in the field of virtualization [6, 32]. The x86 architecture, which has historically not supported hardware virtualization, has now been extended. Instead of relying on paravirtualization [32] or intricate binary translation from Virtual Machine Monitors (VMMs) such as VMware Workstation [40], virtualization in hardware is now directly supported by all major x86 CPU manufacturers [6]. One field able to take advantage of hardware virtualization is High-Performance Computing (HPC). In general, HPC users do not care about the space and time multiplexing that hardware virtualization provides. They are more focused on pushing the limits of CPU performance and memory size. Because they are trying to push these limits, HPC tends to require a significant portion of operating system customization. Most HPC applications provide extremely different workloads than those provided by typical servers or workstations [32]. Virtualization is able to aid with this operating system customization, and now that VMMs have easier direct hardware access, their full potential can be explored. Virtualization allows for the quick creation and destruction of multiple operating system instances on a single machine. This significantly decreases the cost of HPC by removing the need to purchase expensive data clusters. Virtual clusters can be created, and each individual virtual machine can run a specialized operating system to better utilize the hardware running underneath [32]. One such attempt at a specialized operating system is the Low-LAtency Minimal Appliance Operating System (or LlamaOS) [29] being de- veloped at the University of Cincinnati. LlamaOS works by launching a virtualized cluster of LlamaOS 1 CHAPTER 1. INTRODUCTION 1.1. MOTIVATION virtual machines. Communication between nodes within a LlamaOS cluster is achieved by LlamaNET. Lla- maNET was developed as a high performance, lightweight communication protocol to decreased the latency between the machines in a cluster and boost I/O and parallel computation performance. Testing showed that LlamaNET was a massive success, and that it could reduce latency by an order of magnitude over native networking applications for message sizes below 1KB [20]. This opened up the idea to further improve LlamaOS and explore different avenues to decrease parallel simulation runtime; however, before further performance improvements could be made, additional modules needed to be added to the core of the LlamaOS solution. The first of these improvements was the addition of a virtual file system [12] and a driver to support the second extended file system (Ext2) [35]. 1.1 Motivation Although LlamaOS has the capability to show significant one-way message passing latency decreases with the use of LlamaNET [29], it still has a lot of areas that are underdeveloped. The first of these areas is file system I/O. Until 2013 LlamaOS lacked the capability for applications to have their own specific configuration files. This was largely an issue for the more complex WARPED [30] simulation models that required a configuration file detailing many different running parameters. A quick fix was created to solve this issue that involved the implementation of support for a single-file file system. This was a flat file system that contained no directory structure and was only able to contain a single configuration file. The current limitations with the file system are as follows [20]: • The file needs to be statically declared and loaded into memory at the start of the instance. • The file is read-only and new files cannot be created. • The file system does not contain directories or any hierarchical structure. • The file needs to be padded to 512 byte segments. These limitations hinder the ability of LlamaOS to perform in depth testing of simulation models that require even the most basic of file system operations. 2 CHAPTER 1. INTRODUCTION 1.2. THESIS OVERVIEW To overcome these limitations this thesis explores the expansion of LlamaOS to incorporate a Virtual File System (VFS) and a second extended file system (Ext2) driver. These changes allow LlamaOS to perform basic yet necessary operations to a single disk formatted with the Ext2 file system.
Recommended publications
  • JSON Hijacking for the Modern Web About Me
    JSON hijacking For the modern web About me • I’m a researcher at PortSwigger • I love hacking JavaScript let:let{let:[x=1]}=[alert(1)] • I love breaking browsers • @garethheyes History of JSON hijacking • Array constructor attack function Array(){ for(var i=0;i<this.length;i++) { alert(this[i]); } } [1,2,3] • Found by Joe Walker in 2007 • Worked against Gmail in 2007 by Jeremiah Grossman • Fixed in every browser History of JSON hijacking • Object.prototype setter attack Object.prototype.__defineSetter__('user', function(obj){ for(var i in obj) { alert(i + '=' + obj[i]); } }); [{user:{name:"test"}}] • Worked against Twitter • Fixed in every browser Journey of bug discovery James:Can you create a polyglot js/jpeg? Me:Yeah, that sounds like fun. “Polyglot is something that executes in more than one language or format” Anatomy of a jpeg FF D8 FF E0 Anatomy of a jpeg • Start of image marker: FF D8 • Application header: FF E0 00 00 Two bytes we control Anatomy of a jpeg • Guess which two bytes I chose? Rest of app header Valid JS variable • 2F 2A JS comment • /* • FF D8 FF E0 2F 2A 4A 46 49 46 00 01 01 01 00 48 00 48 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00… Padding of nulls for 0x2f2a Anatomy of a jpeg • Inject our payload inside a jpeg comment • FF FE 00 1C • */=alert("Burp rocks.")/* Anatomy of a jpeg • At the end of the image we need to modify the image data • Close our comment • Inject a single line comment after • */// • 2A 2F 2F 2F FF D9 Anatomy of a jpeg • That should work right? <script src="polyglot/uploads/xss.jpg"></script>
    [Show full text]
  • Introduction to JSON (Javascript Object Notation)
    IInnttrroodduuccttiioonn ttoo JJSSOONN ((JJaavvaaSSccrriipptt OObbjjeecctt NNoottaattiioonn)) SSaanngg SShhiinn JJaavvaa TTeecchhnonollogogyy AArrcchhiitteecctt SSunun MMiiccrrososyysstteemmss,, IIncnc.. ssaanngg..sshhiinn@@ssunun..ccoomm wwwwww..jjaavvaapapassssiioon.n.ccoomm Disclaimer & Acknowledgments ● Even though Sang Shin is a full-time employee of Sun Microsystems, the contents here are created as his own personal endeavor and thus does not reflect any official stance of Sun Microsystems 2 Topics • What is JSON? • JSON Data Structure > JSON Object > JSON text • JSON and Java Technology • How to send and receive JSON data at both client and server sides • JSON-RPC • Resources 3 WWhhaatt iiss && WWhhyy JJSSOONN?? What is JSON? • Lightweight data-interchange format > Compared to XML • Simple format > Easy for humans to read and write > Easy for machines to parse and generate • JSON is a text format > Programming language independent > Uses conventions that are familiar to programmers of the C- family of languages, including C, C++, C#, Java, JavaScript, Perl, Python 5 Why Use JSON over XML • Lighter and faster than XML as on-the-wire data format • JSON objects are typed while XML data is typeless > JSON types: string, number, array, boolean, > XML data are all string • Native data form for JavaScript code > Data is readily accessible as JSON objects in your JavaScript code vs. XML data needed to be parsed and assigned to variables through tedious DOM APIs > Retrieving values is as easy as reading from an object property in your JavaScript
    [Show full text]
  • OCF Core Optional 2.1.0
    OCF Core - Optional Specification VERSION 2.1.0 | November 2019 CONTACT [email protected] Copyright Open Connectivity Foundation, Inc. © 2019 All Rights Reserved. 2 Legal Disclaimer 3 4 NOTHING CONTAINED IN THIS DOCUMENT SHALL BE DEEMED AS GRANTING YOU ANY KIND 5 OF LICENSE IN ITS CONTENT, EITHER EXPRESSLY OR IMPLIEDLY, OR TO ANY 6 INTELLECTUAL PROPERTY OWNED OR CONTROLLED BY ANY OF THE AUTHORS OR 7 DEVELOPERS OF THIS DOCUMENT. THE INFORMATION CONTAINED HEREIN IS PROVIDED 8 ON AN "AS IS" BASIS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, 9 THE AUTHORS AND DEVELOPERS OF THIS SPECIFICATION HEREBY DISCLAIM ALL OTHER 10 WARRANTIES AND CONDITIONS, EITHER EXPRESS OR IMPLIED, STATUTORY OR AT 11 COMMON LAW, INCLUDING, BUT NOT LIMITED TO, IMPLIED WARRANTIES OF 12 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OPEN CONNECTIVITY 13 FOUNDATION, INC. FURTHER DISCLAIMS ANY AND ALL WARRANTIES OF NON- 14 INFRINGEMENT, ACCURACY OR LACK OF VIRUSES. 15 The OCF logo is a trademark of Open Connectivity Foundation, Inc. in the United States or other 16 countries. *Other names and brands may be claimed as the property of others. 17 Copyright © 2016-2019 Open Connectivity Foundation, Inc. All rights reserved. 18 Copying or other form of reproduction and/or distribution of these works are strictly prohibited. 19 Copyright Open Connectivity Foundation, Inc. © 2016-2019. All rights Reserved 20 CONTENTS 21 1 Scope .............................................................................................................................
    [Show full text]
  • Understanding JSON Schema Release 2020-12
    Understanding JSON Schema Release 2020-12 Michael Droettboom, et al Space Telescope Science Institute Sep 14, 2021 Contents 1 Conventions used in this book3 1.1 Language-specific notes.........................................3 1.2 Draft-specific notes............................................4 1.3 Examples.................................................4 2 What is a schema? 7 3 The basics 11 3.1 Hello, World!............................................... 11 3.2 The type keyword............................................ 12 3.3 Declaring a JSON Schema........................................ 13 3.4 Declaring a unique identifier....................................... 13 4 JSON Schema Reference 15 4.1 Type-specific keywords......................................... 15 4.2 string................................................... 17 4.2.1 Length.............................................. 19 4.2.2 Regular Expressions...................................... 19 4.2.3 Format.............................................. 20 4.3 Regular Expressions........................................... 22 4.3.1 Example............................................. 23 4.4 Numeric types.............................................. 23 4.4.1 integer.............................................. 24 4.4.2 number............................................. 25 4.4.3 Multiples............................................ 26 4.4.4 Range.............................................. 26 4.5 object................................................... 29 4.5.1 Properties...........................................
    [Show full text]
  • Convert Json Into Html Table
    Convert Json Into Html Table Unsatisfying and insufficient Ephrayim run-throughs her wavemeters outbalanced or uncoils brassily. Smoke-dried Waring Tedstill serialises: criticizes her derogate throttle and precinct sea-level alkalising Percival and frog seaplane quite mighty desolately. but inures her complacency vividly. Ralline and usufruct Now should return the question is that makes it as a little bit more readable html table into an array into the table header, with intent to In out output html file because i our trying to convert their huge json data. Json-to-HTML-Table 101 NuGet Gallery. Use this tool for convert JSON into an HTML Table And thanks to the MySQL JSONTABLE function we operate always transform the JSON objects into unique virtual. Ankitaps You survive try using Dataweave to convert JSON to XML and probably use XSLT to convert XML to HTML Or simply you read try using. ResponseText convert soap response object a json object appendjsondata pass the. Productivity picks for contributing an html table into the query because checkboxes allow multiple values? My knowledge approach you I built it 4-5 years ago so to embed JSON data augment the HTML page and sludge use JavaScript to crumple that JSON data. When there was this follow users and we only work fast, indentation and beautify and read data into an html generation part goes inside html table into json html tables from an online? Convert JSON to HTML Tool Slick. DOCTYPE html 2 3 4 Convert JSON Data to HTML Table 5 6 th td p input 7 font14px Verdana.
    [Show full text]
  • The Latest IBM Z COBOL Compiler: Enterprise COBOL V6.2!
    The latest IBM Z COBOL compiler: Enterprise COBOL V6.2! Tom Ross Captain COBOL SHARE Providence August 7,2017 1 COBOL V6.2 ? YES! • The 4 th release of the new generation of IBM Z COBOL compilers • Announced: July 17, 2017 • The same day as IBM z14 hardware…coincidence? • GA: September 8, 2017 • Compiler support for the new IBM z14 hardware and IBM z/OS V2.3 • Ability to exploit the new Vector Packed Decimal Facility of z14 • ‘OLD’ news: • COBOL V5 EOM Sept 11, 2017 (announced Dec 6, 2016) • EOS for COBOL V4 ‘might’ be earlier than 2020, still discussing 2 COBOL V6.2 ? What else does it have? • New and changed COBOL statements, such as the new JSON PARSE statement • Support of COBOL 2002/2014 standards with the addition of the COBOL Conditional Compilation language feature • New and changed COBOL options for increased flexibility • Improved compiler listings with compiler messages at the end of the listing as in previous releases of the compiler • Improved interfaces to optional products and tools such as IBM Debug for z Systems (formerly Debug Tool for z/OS) and IBM Application Discovery and Delivery Intelligence (formerly EzSource) • Compile-time and runtime performance enhancements • Improved usability of the compiler in the z/OS UNIX System Services environment 3 Vector Packed Decimal Facility of z14 • Enterprise COBOL V6.2 adds support for exploiting the new Vector Packed Decimal Facility in z14 through the ARCH(12) compiler option. • The Vector Packed Decimal Facility allows the dominant COBOL data types, packed and zoned decimal, to be handled in wide 16-byte vector registers instead of in memory.
    [Show full text]
  • Plain Text & Character Encoding
    Journal of eScience Librarianship Volume 10 Issue 3 Data Curation in Practice Article 12 2021-08-11 Plain Text & Character Encoding: A Primer for Data Curators Seth Erickson Pennsylvania State University Let us know how access to this document benefits ou.y Follow this and additional works at: https://escholarship.umassmed.edu/jeslib Part of the Scholarly Communication Commons, and the Scholarly Publishing Commons Repository Citation Erickson S. Plain Text & Character Encoding: A Primer for Data Curators. Journal of eScience Librarianship 2021;10(3): e1211. https://doi.org/10.7191/jeslib.2021.1211. Retrieved from https://escholarship.umassmed.edu/jeslib/vol10/iss3/12 Creative Commons License This work is licensed under a Creative Commons Attribution 4.0 License. This material is brought to you by eScholarship@UMMS. It has been accepted for inclusion in Journal of eScience Librarianship by an authorized administrator of eScholarship@UMMS. For more information, please contact [email protected]. ISSN 2161-3974 JeSLIB 2021; 10(3): e1211 https://doi.org/10.7191/jeslib.2021.1211 Full-Length Paper Plain Text & Character Encoding: A Primer for Data Curators Seth Erickson The Pennsylvania State University, University Park, PA, USA Abstract Plain text data consists of a sequence of encoded characters or “code points” from a given standard such as the Unicode Standard. Some of the most common file formats for digital data used in eScience (CSV, XML, and JSON, for example) are built atop plain text standards. Plain text representations of digital data are often preferred because plain text formats are relatively stable, and they facilitate reuse and interoperability.
    [Show full text]
  • JSON JSON (Javascript Object Notation) Ecmascript Javascript
    ECMAScript JSON ECMAScript is standardized JavaScript. The current version is the 12th edition: Péter Jeszenszky Ecma International, ECMAScript 2021 Language Specification, Standard ECMA-262, 12th ed., June 2021. https://www.ecma- international.org/publications-and-standards/standards/ecma-262/ October 8, 2021 The next version currently under development is ECMAScript 2022: ECMAScript 2022 Language Specification https://tc39.es/ecma262/ Péter Jeszenszky JSON October 8, 2021 1 / 94 Péter Jeszenszky JSON October 8, 2021 3 / 94 JSON (JavaScript Object Notation) JavaScript Lightweight, textual, and platform independent data exchange format. Used for representing structured data. The term JavaScript is used for the implementations of ECMAScript by different vendors. Can be read and written easily by humans. See also: JavaScript technologies overview Can be generated and processed easily by computer programs. https://developer.mozilla.org/en- US/docs/Web/JavaScript/JavaScript_technologies_overview Originates from the ECMAScript programming language. Website: https://www.json.org/ Péter Jeszenszky JSON October 8, 2021 2 / 94 Péter Jeszenszky JSON October 8, 2021 4 / 94 JavaScript Engines (1) Node.js (1) SpiderMonkey (written in: C/C++; license: Mozilla Public License 2.0) https://spidermonkey.dev/ A JavaScript runtime environment built on the V8 JavaScript engine The JavaScript engine of the Mozilla Project. that is designed to build scalable network applications. V8 (written in: C++; license: New BSD License) https://v8.dev/ Website: https://nodejs.org/ https://github.com/nodejs/node https://github.com/v8/v8/ License: MIT License The JavaScript engine of Chromium. Written in: C++, JavaScript JavaScriptCore (written in: C++; license: LGPLv2) https://developer.apple.com/documentation/javascriptcore https: Platform: Linux, macOS, Windows //github.com/WebKit/webkit/tree/master/Source/JavaScriptCore The JavaScript engine developed for the WebKit rendering engine.
    [Show full text]
  • International Standard Iso/Iec 9075-2
    This is a previewINTERNATIONAL - click here to buy the full publication ISO/IEC STANDARD 9075-2 Fifth edition 2016-12-15 Information technology — Database languages — SQL — Part 2: Foundation (SQL/Foundation) Technologies de l’information — Langages de base de données — SQL — Partie 2: Fondations (SQL/Fondations) Reference number ISO/IEC 9075-2:2016(E) © ISO/IEC 2016 ISO/IEC 9075-2:2016(E) This is a preview - click here to buy the full publication COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2016, Published in Switzerland All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form orthe by requester. any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of Ch. de Blandonnet 8 • CP 401 ISOCH-1214 copyright Vernier, office Geneva, Switzerland Tel. +41 22 749 01 11 Fax +41 22 749 09 47 www.iso.org [email protected] ii © ISO/IEC 2016 – All rights reserved This is a preview - click here to buy the full publication ISO/IEC 9075-2:2016(E) Contents Page Foreword..................................................................................... xxi Introduction.................................................................................. xxii 1 Scope.................................................................................... 1 2 Normative references.....................................................................
    [Show full text]
  • 2021-2022 Recommended Formats Statement
    Library of Congress Recommended Formats Statement 2021-2022 For online version, see Recommended Formats Statement - 2021-2022 (link) Introduction to the 2021-2022 revision ....................................................................... 3 I. Textual Works ...................................................................................................... 5 i. Textual Works – Print (books, etc.) ........................................................................................................... 5 ii. Textual Works – Digital ............................................................................................................................ 7 iii. Textual Works – Electronic serials .......................................................................................................... 9 II. Still Image Works ............................................................................................... 12 i. Photographs – Print ................................................................................................................................ 12 ii. Photographs – Digital............................................................................................................................. 13 iii. Other Graphic Images – Print (posters, postcards, fine prints) ............................................................ 14 iv. Other Graphic Images – Digital ............................................................................................................. 15 v. Microforms ...........................................................................................................................................
    [Show full text]
  • ISO/IEC Version of ECMA-404
    © ISO/IEC 2015 – All rights reserved Ecma/TC39/2015/025 ISO/IEC JTC 1/SC 22 First edition 2015-mm-dd ISO/IEC XXXXX:2015 (E) ISO/IEC/JTC 1/SC 22 Secretariat: ANSI Information technology — Programming languages, their environments and system software interfaces — The JSON Data Interchange Format Document type: International standard Document subtype: if applicable Document stage: (20) Preparation Document language: E ISO/IEC XXXXX:2015(E) Copyright notice This ISO document is a Draft International Standard and is copyright-protected by ISO. Except as permitted under the applicable laws of the user's country, neither this ISO draft nor any extract from it may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, photocopying, recording or otherwise, without prior written permission being secured. Requests for permission to reproduce should be addressed to either ISO at the address below or ISO's member body in the country of the requester. ISO copyright office Case postale 56 • CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail [email protected] Web www.iso.org Reproduction may be subject to royalty payments or a licensing agreement. Violators may be prosecuted. ii © ISO/IEC 2015 – All rights reserved ISO/IEC XXXXX:2015(E) Contents Page 1 Scope ....................................................................................................................................................... 1 2 Conformance .........................................................................................................................................
    [Show full text]
  • CAT Reporting Customer & Account Technical Specifications for Industry
    CAT Reporting Customer & Account Technical Specifications for Industry Members 4/21/2020 Version 1.1 Table of Contents Preface ........................................................................................................................................................ iii Executive Summary ................................................................................................................................... iv 1. Introduction ......................................................................................................................................... 1 1.1. CAT Overview ............................................................................................................................. 1 2. CAT Customer & Account Reporting Fundamentals ...................................................................... 2 2.1. Key Data Elements ..................................................................................................................... 2 Firm Identifiers in File Submissions ........................................................................... 2 2.2. Reference Data ........................................................................................................................... 2 Firm Designated ID (FDID) ........................................................................................... 2 Large Trader ID (LTID) and Unidentified Large Trader ID (ULTID)........................... 3 FDID Open Date ...........................................................................................................
    [Show full text]