DOCSLIB.ORG

The 2016 SNIA Dictionary

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The 2016 SNIA Dictionary A glossary of storage networking data, and information management terminology SNIA acknowledges and thanks its Voting Member Companies: Cisco Cryptsoft DDN Dell EMC Evaluator Group Fujitsu Hitachi HP Huawei IBM Intel Lenovo Macrosan Micron Microsoft NetApp Oracle Pure Storage Qlogic Samsung Toshiba Voting members as of 5.23.16 Storage Networking Industry Association Your Connection Is Here Welcome to the Storage Networking Industry Association (SNIA). Our mission is to lead the storage industry worldwide in developing and promoting standards, technologies, and educational services to empower organizations in the management of information. Made up of member companies spanning the global storage market, the SNIA connects the IT industry with end-to-end storage and information management solutions. From vendors, to channel partners, to end users, SNIA members are dedicated to providing the industry with a high level of knowledge exchange and thought leadership. An important part of our work is to deliver vendor-neutral and technology-agnostic information to the storage and data management industry to drive the advancement of IT technologies, standards, and education programs for all IT professionals. For more information visit: www.snia.org The Storage Networking Industry Association 4360 ArrowsWest Drive Colorado Springs, Colorado 80907, U.S.A. +1 719-694-1380 The 2016 SNIA Dictionary A glossary of storage networking, data, and information management terminology by the Storage Networking Industry Association The SNIA Dictionary contains terms and definitions related to storage and other information technologies, and is the storage networking industry's most comprehensive attempt to date to arrive at a common body of terminology for the technologies it represents. The terms go through a rigorous technical review and approval process by the SNIA Technical Council to assure their accuracy. The SNIA Technical Council is a group of industry technical experts elected by the members of the SNIA to guide the SNIA’s technical efforts. Their extensive individual technical backgrounds cover all aspects of storage. The reader should recognize that in this rapidly evolving field, new terminology is constantly being introduced, and common usage is shifting. The SNIA regards this dictionary as a living document, to be updated as necessary to reflect a consensus on common usage, and encourages readers to treat it in that spirit. Comments and suggestions for improvement are gratefully accepted at any time, with the understanding that any submitter of comments or suggestions contributes them to SNIA; and SNIA will therefore own the rights to them. Comments and suggestions may be directed to [email protected]. SNIA Dictionary v.2016.1.ENG Proposals for new terms or definitions, or modifications to existing ones, should be submitted on the form located at: http://www.snia.org/education/dictionary/submittal Currently the dictionary is published online and in PDF format approximately every six months--in spring and fall. A paper version is published, with sponsorship opportunities, each spring. Terms of Use The SNIA hereby grants permission for individuals to use this glossary for personal use only, and for corporations and other business entities to use this glossary for internal use only (including internal copying, distribution, and display), provided that: Any definition reproduced must be reproduced in its entirety with no alteration, and, any document, printed or electronic, in which material from this glossary (or any portion hereof) is reproduced must acknowledge the SNIA copyright on that material, and must credit the SNIA for granting permission for its reuse. Other than as explicitly provided above, you may not make any commercial use of this glossary, sell any or all of this glossary, or distribute this glossary to third parties. All rights not explicitly granted above are expressly reserved to SNIA. In particular, the provisions above do not grant the rights to make any commercial use of this glossary, sell any or all of this dictionary, or distribute this dictionary to third parties. Permission to use this glossary for purposes other than those enumerated above may be requested by e-mailing [email protected]; please include the identity of the requesting individual and/or company and a brief description of the purpose, nature, and scope of the requested use. Copyright © 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012, 2013, 2014, 2015, 2016 Storage Networking Industry Association, All Rights Reserved. Last updated April 1, 2016. Definition Format The format for definitions has changed as of the last half of 2008. Terms are now defined as much as possible using the substitution principle, which states that a term's definition should be substitutable for the term itself in a sentence. In the case that more text is required or deemed helpful, it is contained in one or more separate paragraphs after the definition itself. This text is informative in nature, and while intended to be accurate, is not technically part of the definition itself. SNIA Dictionary v.2016.1.ENG Deprecated Synonyms In many cases, as technology develops, companies are forced to invent new terminology to describe innovations in their products. As the technology matures and vendors attempt to compete and compare their products with others, one or two terms become the most widely used, yet a number of other terms may remain in some use which are basically synonyms for the widely used terms. This causes confusion in the marketplace. To encourage crispness and uniformity in product descriptions, this dictionary lists synonyms of this type as "Deprecated synonym for xxxx," where xxxx is the term determined to have become canonical in the industry. This is to indicate both the meaning of xxxx and guide the reader toward use of the more canonical term. In cases where a synonym is not deprecated, the SNIA does not endorse the use of one synonym over another. Definitions taken from standards documents The SNIA has a strong interest in keeping definitions harmonized across various industry groups and national and international standards bodies. Towards this end, some definitions, especially those pertaining to Fibre Channel and SCSI terms and technologies, have been quoted from the appropriate version of the INCITS standard. In all such cases, the INCITS standard is authoritative. The SNIA dictionary may include terms defined in the the following standards and draft standards: INCITS 302-1998, SCSI Parallel Interface - 2 (SPI-2) INCITS 367-2003, SCSI Parallel Interface - 5 (SPI-5) INCITS 405-2005, SCSI Block Commands - 2 (SBC-2) INCITS 431-2007, Serial Attached SCSI - 2.1 (SAS-2.1) INCITS 447-2008, SCSI Architecture Model - 4 (SAM-4) INCITS 448-2008, SCSI Enclosure Services - 2 (SES-2) INCITS 461-2010, Fibre Channel - Switch Fabric-5 (FC-SW-5) INCITS 462-2010, Fibre Channel - Backbone-5 (FC-BB-5) INCITS 466-2011, Fibre Channel - Single-Byte Command Code Sets - 4 (FC-SB-4) INCITS 467-2011, SCSI Stream Commands - 3 (SSC-3) INCITS 470-2011, Fibre Channel - Framing and Signaling - 3 (FC-FS-3) INCITS 475-2011, Fibre Channel - Inter-Fabric Routing (FC-IFR) INCITS 476-2011, SAS Protocol Layer (SPL) SNIA Dictionary v.2016.1.ENG INCITS 476/AM1-2012, SAS Protocol Layer Amendment #1 (SPL-AM1) INCITS 477-2011, Fibre Channel – Link Service - 2 (FC-LS-2) INCITS 478/AM1-2014, Serial Attach SCSI - 2.1 Amendment #1 (SAS-2.1-AM1) INCITS 479-2011, Fibre Channel - Physical Interface - 5 (FC-PI-5) INCITS 481-2012, Fibre Channel Protocol for SCSI - 4 (FCP-4) INCITS 484-2012, SCSI Media Changer Commands - 3 (SMC-3) INCITS 497-2013, Automation/Drive Interface – Commands - 3 (ADC-3) INCITS 505-2013, SAS Protocol Layer - 2 (SPL-2) INCITS 509-2014, Fibre Channel - Backbone - 6 (FC-BB-6) INCITS 514-2014, SCSI Block Commands - 3 (SBC-3) INCITS 516-2014, SCSI Stream Commands - 4 (SSC-4) INCITS 519-2014, Serial Attached SCSI - 3 (SAS-3) The SNIA wishes to thank ANSI and INCITS for their cooperation in this matter. Copies of INCITS standards may be purchased at ANSI's online store at http://webstore.ansi.org. SNIA Dictionary v.2016.1.ENG Context Hierarchy Most of the terms in this dictionary have meaning primarily in specific sub-contexts of storage networking, such as SCSI or File Systems. The following categories are used to declare the context in which a given definition in this dictionary is held to be valid. No attempt has been made to date to rigorously define these categories, so they remain a guide to understanding, not a formal system. General --Hardware ----Network -------SCSI -------iSCSI -------Fibre Channel -------NVMe -------Infiniband ----Data Communication --Computer System ----Storage System --- Operating System -------Windows --Services Cloud --Management ----Data Management -------Backup -------Data Recovery -------Data Security -------Database -------File System -------Long Term Retention -------Capacity Optimization ----Storage Management --Energy --Standards --Legal The context hierarchy is a work in progress. In part, we are constrained by practice in previous editions of the dictionary. In the above hierarchy representation, context labels indented beneath other context labels represent specializations of the higher-order label concept. Below is an example of how context is indicated: context example [Context] The context is called out in square brackets at the beginning of each definition, as in this example. SNIA Dictionary v.2016.1.ENG Authors The following SNIA volunteers
Load more

Recommended publications
  • DATARMOR and New Tools.Pdf
    JOURNÉE DE RENCONTRE DES UTILISATEURS DU PÔLE DE CALCUL INTENSIF POUR LA MER PIERRE COTTY Le programme de la journée • 9 h 40 - 12 h 10 DATARMOR: nouveau périmètre, nouvelles perspectives • Pause déjeuner : buffet • 14 h 00 - 16 h 30 DATARMOR: nouveaux champs d'applications scientifiques • Poster et Discussions autour d’un pot 17/05/2018 2 DATARMOR AND N E W T O O L S Tina ODAKA DATARMOR 17/05/2018 4 ACCES CLIENTS (10 Gigabit Ethernet connected to IFREMER and INFUSER network (SHOM / IUEM / ENSTA Bretagne Cluster HPC 426 Tflops 11 088 cores 396 Nodes Login nodes PBS Pro; sharing computing Batch system: resources PBS Pro InfiniBand FDR 17/05/2018 5 DATARMOR: not only HPC Cluster SMP Cluster Cluster HPC VIS High speed Cluster SCRATCH Network WEB Infini Band DATA DATAREF HOME DATA 17/05/2018 WORK 6 DISK • DATAREF (LUSTRE, 1.5PB = 1395TiB) • Reference data (next presentation) • DATAWORK (GPFS, 5PB = 4500TiB) • Work data • User space and project space • SCRATCH (LUSTRE 0.5PB) PB ? TiB?? • Scratch file for HPCcomparisons computation. with International System of Units (SI) prefixes • 15 days max one kibibit 1 Kibit = 210 bit = 1024 bit one kilobit 1 kbit = 103 bit = 1000 bit • DATAHOME (NFS, 0.04PB)one mebibyte 1 MiB = (210)2 B = 1 048 576 B • Source codes and softwaresone megabyte 1 MB = (103)2 B = 1 000 000 B • with backup ( tape, inone a gibibytedifferent1 GiBbuilding= (210)3 B) = 1 073 741 824 B one gigabyte 1 GB = (103)3 B = 1 000 000 000 B byte = octet( French) TiB (tebibyte) = Tio (French tébioctet) 17/05/2018 7 Clustre WEB, SMP, VIS • Cluster SMP • 1 node with 240 cores, 5 TB RAM • PBS Pro • Jobs only for huge memory, or many CPU cores.
    [Show full text]
  • Z/OS ♦ Z Machines Hardware ♦ Numbers and Numeric Terms ♦ the Road to Z/OS ♦ Z/OS.E ♦ Z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services
    Mainframes The Future of Mainframes Is Now ♦ z/Architecture ♦ z/OS ♦ z Machines Hardware ♦ Numbers and Numeric Terms ♦ The Road to z/OS ♦ z/OS.e ♦ z/OS Futures ♦ Language Environment ♦ Current Compilers ♦ UNIX System Services by Steve Comstock The Trainer’s Friend, Inc. http://www.trainersfriend.com 800-993-8716 [email protected] Copyright © 2002 by Steven H. Comstock 1 Mainframes z/Architecture z/Architecture ❐ The IBM 64-bit mainframe has been named "z/Architecture" to contrast it to earlier mainframe hardware architectures ♦ S/360 ♦ S/370 ♦ 370-XA ♦ ESA/370 ♦ ESA/390 ❐ Although there is a clear continuity, z/Architecture also brings significant changes... ♦ 64-bit General Purpose Registers - so 64-bit integers and 64-bit addresses ♦ 64-bit Control Registers ♦ 128-bit PSW ♦ Tri-modal addressing (24-bit, 31-bit, 64-bit) ♦ Over 140 new instructions, including instructions to work with ASCII and UNICODE strings Copyright © 2002 by Steven H. Comstock 2 z/Architecture z/OS ❐ Although several operating systems can run on z/Architecture machines, z/OS is the premier, target OS ❐ z/OS is the successor to OS/390 ♦ The last release of OS/390 was V2R10, available 9/2000 ♦ The first release of z/OS was V1R1, available 3/2001 ❐ z/OS can also run on G5/G6 and MP3000 series machines ♦ But only in 31-bit or 24-bit mode ❐ Note these terms: ♦ The Line - the 16MiB address limit of MVS ♦ The Bar - the 2GiB limit of OS/390 ❐ For some perspective, realize that 16EiB is... ♦ 8 billion times 2GiB ♦ 1 trillion times 16MiB ❐ The current release of z/OS is V1R4; V1R5 is scheduled for 1Q2004 Copyright © 2002 by Steven H.
    [Show full text]
  • Broadband/IP/Cloud Computing
    Broadband/IP/Cloud Computing Presentation to the Colorado Telecommunications Association www.cellstream.com (c) 2011 CellStream, Inc. 1 www.cellstream.com (c) 2011 CellStream, Inc. 2 www.cellstream.com (c) 2011 CellStream, Inc. 3 www.cellstream.com (c) 2011 CellStream, Inc. 4 www.cellstream.com (c) 2011 CellStream, Inc. 5 Past vs. Present The Past – 20th Century The Present – 21st Century • Peer-to-Peer with broadcast • Many-to-Many with multicast • Mix of Analog and Digital • All media is digital – single • Producers supply transport Consumers • All media is connected • Peer-to-Peer is 1:1 • Many-to-Many is M:N o Traditional Telephone • Producers and Consumers • Broadcast is 1:N do both o Newspaper o CNN takes reports from Twitter o TV/Radio o End users send pictures and reports www.cellstream.com (c) 2011 CellStream, Inc. 6 Where are we in Phone Evolution? PHONE 1.0 PHONE 2.0 PHONE 3.0 Soft phone Your Phone Number Your Phone Number Your Phone Number represents where you represents you represents an IP Address – are (e.g. 972-747- regardless of where you independent of location 0300 is home, 214- are. and appliance you are 405-3708 is work) using (e.g. IP Phone, Cell Phone, PDA, Computer, Television, etc.) www.cellstream.com (c) 2011 CellStream, Inc. 7 Phone 3.X • Examples of Phone 3.0 are Skype, Google Talk, others on a PC. • Phone 3.1 – Skype on an iTouch • Phone 3.2 – Android OS from Google – a phone Centric OS that runs on cellular appliances • Phone 3.3 – Android OS from Google that runs on a Phone Appliance www.cellstream.com (c) 2011 CellStream, Inc.
    [Show full text]
  • Etir Code Lists
    eTIR Code Lists Code lists CL01 Equipment size and type description code (UN/EDIFACT 8155) Code specifying the size and type of equipment. 1 Dime coated tank A tank coated with dime. 2 Epoxy coated tank A tank coated with epoxy. 6 Pressurized tank A tank capable of holding pressurized goods. 7 Refrigerated tank A tank capable of keeping goods refrigerated. 9 Stainless steel tank A tank made of stainless steel. 10 Nonworking reefer container 40 ft A 40 foot refrigerated container that is not actively controlling temperature of the product. 12 Europallet 80 x 120 cm. 13 Scandinavian pallet 100 x 120 cm. 14 Trailer Non self-propelled vehicle designed for the carriage of cargo so that it can be towed by a motor vehicle. 15 Nonworking reefer container 20 ft A 20 foot refrigerated container that is not actively controlling temperature of the product. 16 Exchangeable pallet Standard pallet exchangeable following international convention. 17 Semi-trailer Non self propelled vehicle without front wheels designed for the carriage of cargo and provided with a kingpin. 18 Tank container 20 feet A tank container with a length of 20 feet. 19 Tank container 30 feet A tank container with a length of 30 feet. 20 Tank container 40 feet A tank container with a length of 40 feet. 21 Container IC 20 feet A container owned by InterContainer, a European railway subsidiary, with a length of 20 feet. 22 Container IC 30 feet A container owned by InterContainer, a European railway subsidiary, with a length of 30 feet. 23 Container IC 40 feet A container owned by InterContainer, a European railway subsidiary, with a length of 40 feet.
    [Show full text]
  • Z/OS, Language Environment, and UNIX How They Work Together
    The Trainer’s Friend, Inc. 256-B S. Monaco Parkway Telephone: (800) 993-8716 Denver, Colorado 80224 (303) 393-8716 U.S.A. Fax: (303) 393-8718 E-mail: [email protected] Internet: www.trainersfriend.com z/OS, Language Environment, and UNIX How They Work Together The following terms that may appear in these materials are trademarks or registered trademarks: Trademarks of the International Business Machines Corporation: AD/Cycle, AIX, AIX/ESA, Application System/400, AS/400, BookManager, CICS, CICS/ESA, COBOL/370, COBOL for MVS and VM, COBOL for OS/390 & VM, Common User Access, CORBA, CUA, DATABASE 2, DB2, DB2 Universal Database, DFSMS, DFSMSds, DFSORT, DOS/VSE, Enterprise System/3090, ES/3090, 3090, ESA/370, ESA/390, Hiperbatch, Hiperspace, IBM, IBMLink, IMS, IMS/ESA, Language Environment, MQSeries, MVS, MVS/ESA, MVS/XA, MVS/DFP, NetView, NetView/PC, Object Management Group, Operating System/400, OS/400, PR/SM, OpenEdition MVS, Operating System/2, OS/2, OS/390, OS/390 UNIX, OS/400, QMF, RACF, RS/6000, SOMobjects, SOMobjects Application Class Library, System/370, System/390, Systems Application Architecture, SAA, System Object Model, TSO, VisualAge, VisualLift, VTAM, VM/XA, VM/XA SP, WebSphere, z/OS, z/VM, z/Architecture, zSeries Trademarks of Microsoft Corp.: Microsoft, Windows, Windows NT, Windows ’95, Windows ’98, Windows 2000, Windows SE, Windows XP Trademark of Chicago-Soft, Ltd: MVS/QuickRef Trademark of Phoenix Software International: (E)JES Registered Trademarks of Institute of Electrical and Electronic Engineers: IEEE, POSIX Registered Trademark of The Open Group: UNIX Trademark of Sun Microsystems, Inc.: Java Registered Trademark of Linus Torvalds: LINUX Registered Trademark of Unicode, Inc.: Unicode Preface This document came about as a result of writing my first course for UNIX on the IBM mainframe.
    [Show full text]
  • Breaking Through the Myths to Reality: a Future-Proof View Of
    Breaking Through the Myths to Reality A Future-Proof View of Fiber Optic Inspection and Cleaning Dear Viewer: As presented at BICSI® in February- 2018, this seminar has video and animations that Edward J. Forrest, Jr. are not available as a .pdf file. If you would like the RMS(RaceMarketingServices) original version, please contact BICSI or the author. Bringing Ideas Together Caution: This Presentation is going to be controversial! IT IS BASED ON 2,500 YEARS OF SCIENCE AND PRODUCT DEVELOPMENT 2 Fact OR FICTION of Fiber Optic Cleaning and Inspection This seminarWE WILL mayDISCUSS contradictAND currentDEFINE: trends ➢ There➢ Cleaningand are what OTHER you’ve is notWAYS been important…BESIDES taught. VIDEO ➢ ➢➢“Automatic99.9%Debris➢ ➢ExistingA “Reagent FiberonS Detection” CIENTIFICthe standards, Optic surface Grade” ConnectorR isEALITY of such“good Isopropanola fiber… as enough”.is optic a is IECconnector“Pass 61300Let’sanI NSPECTIONanythingeffective- Fail”separate- 3surface-35, is is bettereasy are Factsfiberto is “Best determine thantwoto from optic understand nothing!-dimensional Practice”Fiction cleaner What we’veTwoif the ( ALL-Dimensional connector) been taught/bought/soldand is Structure“clean” over the last 30+Myth yearsfrom may“diameter”. Scientific not be the same Reality thing! 3 Fact OR FICTION of Fiber Optic Cleaning and Inspection ➢ A Fiber Optic Connector is a Two-Dimensional Structure ➢ 99.9% “Reagent Grade” Isopropanol is an effective fiber optic cleaner ➢ Cleaning is not important… anything is better than nothing! ➢ There are OTHER WAYS BESIDES VIDEO INSPECTION to determine if the connector is “clean” ➢ Debris on the surface of a fiber optic connector surface is two-dimensional “diameter”. ➢ “Automatic Detection” is “good enough”.
    [Show full text]
  • Course Conventions Fall 2016
    CS168 Computer Networks Fonseca Course Conventions Fall 2016 Contents 1 Introduction 1 2 RFC Terms 1 3 Data Sizes 2 1 Introduction This document covers conventions that will be used throughout the course. 2 RFC Terms For the project specifications in this class, we’ll be using proper RFC terminology. It’s the terminology you’ll see if you ever implement protocols in the real world (e.g., IMAP or MCTCP), so it’s good to get exposed to it now. In particular, we’ll be using the keywords “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” as defined in RFC 2119. The terms we’ll use the most in this class are “MUST”, “MUST NOT”, “SHOULD”, “SHOULD NOT”, and “MAY” (though we may use others occasionally), so we’re including their definitions here for convenience (copied verbatim from the RFC): • MUST This word, or the terms “REQUIRED” or “SHALL”, mean that the definition is an absolute requirement of the specification. • MUST NOT This word, or the phrase “SHALL NOT”, mean that the definition is an absolute prohibition of the specification. • SHOULD This word, or the adjective “RECOMMENDED”, mean that there may exist valid reasons in particular circumstances to ignore a particular item, but the full implications must be understood and carefully weighed before choosing a different course. • SHOULD NOT This phrase, or the phrase “NOT RECOMMENDED”, mean that there may exist valid reasons in particular circumstances when the particular behavior is acceptable or even useful, but the full implications should be understood and the case carefully weighed before implementing any behavior described with this label.
    [Show full text]
  • Bitmath Documentation Release 1.3.3
    bitmath Documentation Release 1.3.3 Tim Bielawa Sep 13, 2018 Contents 1 Installation 3 2 Contents 5 2.1 The bitmath Module..........................................5 2.2 The bitmath command-line Tool................................... 19 2.3 Classes.................................................. 20 2.4 Instances................................................. 23 2.5 Getting Started.............................................. 29 2.6 Real Life Examples........................................... 32 2.7 Contributing to bitmath......................................... 41 2.8 Appendices................................................ 45 2.9 NEWS.................................................. 51 2.10 Contact.................................................. 56 2.11 Copyright................................................. 57 2.12 Examples................................................. 57 Python Module Index 63 i ii bitmath Documentation, Release 1.3.3 bitmath simplifies many facets of interacting with file sizes in various units. Originally focusing on file size unit conversion, functionality now includes: • Converting between SI and NIST prefix units (kB to GiB) • Converting between units of the same type (SI to SI, or NIST to NIST) • Automatic human-readable prefix selection (like in hurry.filesize) • Basic arithmetic operations (subtracting 42KiB from 50GiB) • Rich comparison operations (1024 Bytes == 1KiB) • bitwise operations (<<, >>, &, |, ^) • Reading a device’s storage capacity (Linux/OS X support only) • argparse integration as
    [Show full text]
  • File Organization and Management Com 214 Pdf
    File organization and management com 214 pdf Continue 1 1 UNESCO-NIGERIA TECHNICAL - VOCATIONAL EDUCATION REVITALISATION PROJECT-PHASE II NATIONAL DIPLOMA IN COMPUTER TECHNOLOGY FILE Organization AND MANAGEMENT YEAR II- SE MESTER I THEORY Version 1: December 2 2 Content Table WEEK 1 File Concepts... 6 Bit:... 7 Binary figure... 8 Representation... 9 Transmission... 9 Storage... 9 Storage unit... 9 Abbreviation and symbol More than one bit, trit, dontcare, what? RfC on trivial bits Alternative Words WEEK 2 WEEK 3 Identification and File File System Aspects of File Systems File Names Metadata Hierarchical File Systems Means Secure Access WEEK 6 Types of File Systems Disk File Systems File Systems File Systems Transactional Systems File Systems Network File Systems Special Purpose File Systems 3 3 File Systems and Operating Systems Flat File Systems File Systems according to Unix-like Operating Systems File Systems according to Plan 9 from Bell Files under Microsoft Windows WEEK 7 File Storage Backup Files Purpose Storage Primary Storage Secondary Storage Third Storage Out Storage Features Storage Volatility Volatility UncertaintyAbility Availability Availability Performance Key Storage Technology Semiconductor Magnetic Paper Unusual Related Technology Connecting Network Connection Robotic Processing Robotic Processing File Processing Activity 4 4 Technology Execution Program interrupts secure mode and memory control mode Virtual Memory Operating Systems Linux and UNIX Microsoft Windows Mac OS X Special File Systems Journalized File Systems Graphic User Interfaces History Mainframes Microcomputers Microsoft Windows Plan Unix and Unix-like operating systems Mac OS X Real-time Operating Systems Built-in Core Development Hobby Systems Pre-Emptification 5 5 WEEK 1 THIS WEEK SPECIFIC LEARNING OUTCOMES To understand: The concept of the file in the computing concept, field, character, byte and bits in relation to File 5 6 6 Concept Files In this section, we will deal with the concepts of the file and their relationship.
    [Show full text]
  • IBM-IS-DCI-UR-Newsletter.Pdf
    Monthly Newsletter Mar 2016 Monthly Journal on Technology Know-How of IBM’s Technology space Tech Updates on Mainframe Platform “Mainframe“ the IBM Dictionary Of Computing defines "mainframe" as "a large computer, in particular one to which other computers can be connected so that they can share facilities the mainframe provides (for example, a System/370 computing system to which personal computers are attached so that they can upload and download programs and data). The term “Mainframe “ usually refers to hardware only, namely, main storage, execution circuitry and peripheral units“ level, as opposed to trying to do it all from the System z platform. Did you know that mainframes and all other computers have two types of physical storage: Internal and external. Physical storage located on the mainframe processor itself. This is called processor storage, real storage or central storage; think of it as memory for the mainframe. Physical storage external to the mainframe, including storage on direct access devices, such as disk drives and tape drives. This storage is called paging storage or auxiliary storage. The primary difference between the two kinds of storage relates to the way in which it is accessed, as follows: Central storage is accessed synchronously with the processor. That is, the processor must wait while data is retrieved from central storage. Auxiliary storage is accessed asynchronously. The processor accesses auxiliary storage through an input/output (I/O) request, which is scheduled to run amid other work requests in the system. During an I/O request, the processor is free to execute other, unrelated work.
    [Show full text]
  • Prefixes for Binary Multiples
    Definitions of the SI units: The binary prefixes Page 1 of 3 Return to Prefixes for binary multiples Units home page In December 1998 the International Electrotechnical Commission (IEC), the leading international organization for worldwide Units standardization in electrotechnology, approved as an IEC Topics: International Standard names and symbols for prefixes for binary Introduction multiples for use in the fields of data processing and data Units transmission. The prefixes are as follows: Prefixes Outside Prefixes for binary multiples Rules Background Factor Name Symbol Origin Derivation 210 kibi Ki kilobinary: (210)1 kilo: (103)1 Units 220 mebi Mi megabinary: (210)2 mega: (103)2 Bibliography 230 gibi Gi gigabinary: (210)3 giga: (103)3 Constants, 240 tebi Ti terabinary: (210)4 tera: (103)4 Units & 50 pebi Pi 10 5 3 5 Uncertainty 2 petabinary: (2 ) peta: (10 ) home page 260 exbi Ei exabinary: (210)6 exa: (103)6 Examples and comparisons with SI prefixes one kibibit 1 Kibit = 210 bit = 1024 bit one kilobit 1 kbit = 103 bit = 1000 bit one mebibyte 1 MiB = 220 B = 1 048 576 B one megabyte 1 MB = 106 B = 1 000 000 B one gibibyte 1 GiB = 230 B = 1 073 741 824 B one gigabyte 1 GB = 109 B = 1 000 000 000 B It is suggested that in English, the first syllable of the name of the binary-multiple prefix should be pronounced in the same way as the first syllable of the name of the corresponding SI prefix, and that the second syllable should be pronounced as "bee." It is important to recognize that the new prefixes for binary multiples are not part of the International System of Units (SI), the modern metric system.
    [Show full text]
  • A Practical Introduction to Computer Architecture
    A Practical Introduction to Computer Architecture Daniel Page [email protected] h i git # ba293a0e @ 2019-11-14 © Daniel Page [email protected] h i git # ba293a0e @ 2019-11-14 2 © Daniel Page [email protected] h i MATHEMATICAL PRELIMINARIES In Mathematics you don’t understand things. You just get used to them. – von Neumann The goal of this Chapter is to provide a fairly comprehensive overview of theory that underpins the rest of the book. At first glance the content may seem a little dry, and is often excluded in other similar books. It seems clear, however, that without a solid understanding of said theory, using the constituent topics to solve practical problems will be much harder. The topics covered all relate to the field of discrete Mathematics; they include propositional logic, sets and functions, Boolean algebra and number systems. These four topics combine to produce a basis for formal methods to describe, manipulate and implement digital systems. Readers with a background in Mathematics or Computer Science might skip this Chapter and use it simply for reference; those approaching it from some other background would be advised to read the material in more detail. 1 Propositional logic Definition 0.1. A proposition is a statement whose meaning, termed the truth value, is either true or false (less formally, we say the statement is true if it has a truth value of true and false if it has a truth value of false). A given proposition can involve one or more variables; only when concrete values are assigned to the variables can the meaning of a proposition be evaluated.
    [Show full text]