DOCSLIB.ORG

~:-:~~~ RT Personal Computer Technology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
~:-:~~~ RT Personal Computer Technology • ~:-:~~~ RT Personal Computer Technology - Form No. SA23-1057 Foreword Copyright IBM RT Personal Computer Technology is a A variety of structures and levels of detail ©Copyright International Business Machines collection of papers by the developers of the may exist in the papers because they were Corporation, 1986. Inquiries related to RT PC. These papers describe the innovative written as technical articles by different permission to republish an article in full or in aspects of the RT PC-what we set out to specialists. In order to preserve their part should be directed to the IBM build, how we built it, and how it works today. authenticity and vitality, the papers have not Corporation, IBM Austin, 854/003, 11400 The papers were written by technical been revised for consistency of style or Burnet Road, Austin, TX 78758. professionals for readers who are conversant method of presentation. These papers will not with the vocabulary and concepts of be updated to incorporate future Copies of this book, SA23-1 057, can be computers and programming. developments. obtained from the local IBM branch office. IBM employees can order copies from This book is a one-time statement by the This book is the work of many hands, but Mechanicsburg. developers for historical and background special acknowledgment is due to Bert Buller purposes. Although there are several of the Hardware Architecture Group for Cover: An IBM RT Personal Computer Model overview articles that describe how the coordinating the engineering articles, and to 10 with a larger and somewhat faster various components work together, the Herb Michaelson, Publications Consultant, for ancestor in the background-an IBM System! emphasis is on the novel parts of the RT PC shaping both the book and the individuai 370 Model 158 MP. system. IBM RT Personal Computer articles. Technology is intended to supply the reader with an understanding of the things that make Frank Waters, Editor the RT PC unique, not to provide detailed descriptions of all of the elements of the RT PC system. The papers in this book are not intended to replace IBM publications in describing the capabilities of the system components and how to use them. Keep in mind that the papers are for general technical communication purposes; they do not represent an IBM warranty or commitment to specific capabilities in the referenced products. Preface Introducing a new architecture to the • a resource manager to provide virtual The development of the RT PC system has computer marketplace is never done casually. machine, storage, and 1/0 functions and to been a mUlti-location effort. We have The cost and effort of transition from one ensure data integrity and processing incorporated architectural advances from architecture to another must be justified by continuity, Yorktown Heights, technology innovations substantial advantages. It is always tempting from Burlington, graphics peripherals and to apply advances in technology to improving • a multitasking, multiuser operating system applications from Kingston, and engineering the performance of existing architectures. that can be tailored to make the RT PC and programming developments from Austin. Ultimately, however, refinement is subject to suitable for a variety of user requirements, The RT PC has been the work of hundreds of the law of diminishing returns. Continuing individuals, both within and outside of IBM. advancement requires fundamental changes. • a coprocessor feature that allows users to The articles in this book describe some of run programs written for the IBM PC their contributions. I want to convey to The hardware and software architectures that without interfering with the normal everyone involved my gratitude for their were originally created for personal operation of the RT PC, efforts and my respect for their computers had to accommodate the speed accomplishments. and size constraints of the processors and • and a wide variety of displays, printers, storage devices that were available at the communications adapters, and processing W. Frank King time. Techniques that were known to be features, Group Director of Advanced Engineering effective on mainframes and minicomputers Systems Development were simply too costly to implement on • in a box that fits on or under a desk. Engineering Systems Products personal computers. Our intent in designing independent Business Unit the RT PC has been to use recent With the RT PC, the architectural technological and architectural advances to sophistication of the personal computer has avoid the structural limitations of earlier caught up with that of the mainframe. designs. Perhaps more important, we have laid a foundation for more efficient exploitation of The IBM RT PC is a new synthesis of future advances in both hardware and computer concepts. It combines: software technology. The open-ended ness of the resource manager and operating system • A very fast Reduced Instruction Set 32-bit at all levels means that we can easily take processor for efficient execution of advantage of new applications, devices, and programs compiled from a higher-level communications techniques. language, Ii ---- RT Personal Computer Technology ~ : :i~~ IBM Product Design and Development ® Engineering Systems Products Contents IBM RT PC Architecture and Design Decisions G. Glenn Henry 2 Hardware Description P.O. Hester, J.T. Hollaway, and F.T. May 6 Processor Card D.E. Waldecker, K.G. Wilcox, J.R. Barr, 12 W.T. Glover, C.G. Wright, H. Hoffman System Memory Cards Ronald E. Rowland 18 Floating Point Accelerator Scott M. Smith 21 System Board and I/O Channel for the IBM RT PC Sheldon L. Phelps and John D. Upton 26 System IBM RT PC Displays and Adapters Joe C. St. Clair 31 Use of Artificial Intelligence to Diagnose Nancy A. Burns and C. Edward Williams 35 Hardware Manufacturing Innovations to Increase Quality Charles W. Bartlett, A.V. Burghart, 40 and Reduce Cost George M. Yanker ROMP/MMU Technology Introduction D.E. Waldecker and P.Y. Woon 44 The IBM RT PC ROMP and Memory Management P.O. Hester, Richard O. Simpson, 48 Unit Architecture Albert Chang ROMP/MMU Implementation D.E. Waldecker, C.G. Wright, 57 M.S. Schmookler, T.G. Whiteside, R.D. Groves, C.P. Freeman, A. Torres iii ROMP/MMU Circuit Technology and Chip Design Raymond A. DuPont, Ed Seewann, 66 Peter McCormick, Charles K. Erdelyi, Mukesh P. Patel, P.T. Patel Software Development Tools for ROMP Alan MacKay and Ahmed Chi bib 72 Compiling for the RT PC ROMP M.E. Hopkins 76 Advanced Interactive Executive (AIXTM) Larry Loucks 83 Operating System Structure Restructuring the AIX User Interface P.J. Kilpatrick and Carolyn Greene 88 Configuration Methods for a Personal Computer Shirley Lerom, Lee Terrell, and Hira Advani 91 System IBM RT PC AIX Kernel - Modifications and Larry Loucks 96 Extensions Extendable High-Level AIX User Interface Tom Murphy and Dick Verburg 110 Extended File Management for AIX John M. Bissell 114 The Virtual Resource Manager Thomas G. Lang, Mark S. Greenberg, and 119 Charles H. Sauer Design of the IBM RT PC Virtual Memory Manager J.C. O'Quin, J.T. O'Quin, Mark D. Rogers, 126 T.A. Smith The IBM RT PC Subroutine Linkage Convention J.C.O'Quin 131 Implementation of a Virtual Terminal Subsystem D.C. Baker, G.A. Flurry, K.D. Nguyen 134 Use of a Coprocessor for Emulating the PC AT John W. Irwin 137 Coprocessor Software Support Rajan Krishnamurty and Terry Mothersole 142 PC DOS Emulation in the AIX Environment Leonard F. Brissette, Roy A. Clauson, 147 Jack E. Olson Authors 149 iv Reader's Guide The IBM RT Personal Computer Technology Overview Articles Operating System Modifications and book is divided into four parts. The first Henry 2 Extensions describes the main hardware elements of the Hester et al. 6 Loucks 83 RT PC system. The second section discusses Waldecker and Woon 44 Loucks 96 the RT PC's 32-bit microprocessor. The third Loucks 83 Bissell 114 section covers the RT PC software and the O'Quin 131 fourth the PC AT coprocessor and AIX's PC Major Hardware Components DOS emulation functions. Waldecker et al. 12 Virtual Resource Manager Rowland 18 Lang et al. 119 A reader's guide, for a topical approach to Smith 21 O'Quin et al. 126 this book, is as follows: Phelps and Upton 26 Baker et al. 134 St. Clair 31 Brissette et al. 147 RT PC Microprocessor PC AT Coprocessor Waldecker and Woon 44 Irwin 137 Hester et al. 48 Krishnamurty and Mothersole 142 Waldecker et al. 57 DuPont et al. 66 User Interface Kilpatrick and Greene 88 Lerom et al. 91 Murphy and Verburg 110 Brissette et al. 131 1 IBM RT PC Architecture and Design Decisions G. Glenn Henry Introduction In addition to these technical objectives, there Ported Applications / New Applications The architect of a new system must start by were a number of important practical Application lEt d d 0 making a series of high-level decisions about requirements relative to producing a D I t x en e perar Ing : PC C . .. e~~ ?pmen I System Functions I ompatlblhty the hardware and software structure. These successful product: __ .£~h~S___ .1. _______ ..1 ________ early choices shape all of the ultimate details of the product. An understanding of the • Easy portability of existing IBM and non­ Base Operating System "reasons why" is important to the person IBM applications who is trying the understand the resulting VRM system. In this paper, I will give a very • Easy migration of users and their general overview of the structure of the RT applications and data from existing systems Processor and Memory PC AT Coprocessor PC and explain the rationale for each of the Management Unit major decisions that dictated that structure. • The ability to take advantage of I/O attachments and devices used on other I/O Channel and Devices Product Objectives systems The original objective of the project that resulted in the RT PC was to build a high­ • Straightforward ways for other IBM and Figure 1 Logical Structure of the RT PC function workstation with capabilities far non-IBM development areas to add and beyond those of personal computers.
Load more

Recommended publications
  • IBM RTC PC | User Setup Guide and Options
    Personal Canputer Hardware Reference Library IBM RT PC User Setup Guide SA23-2608-0 c c The following statement applies to this IBM product. The statement for other IBM products intended for use with this product will appear in their accompanying manuals. Federal Communications Commission (FCC) Statement Warning: This equipment generates, uses, and can radiate radio frequency energy and if not installed and used in accordance with the instructions manual, may cause interference to radio communications. It has been tested and found to comply with the limits for a Class A computing device pursuant to Subpart J of Part 15 of FCC Rules, which are designed to provide reasonable protection against such interference when operated in a commercial environment. Operation of this equipment in a residential area is likely to cause interference in which case the user at his own expense will be required to take whatever measures may be required to correct the interference. Instructions to User: Properly shielded and grounded cables and connectors must be used for connection to peripherals in order to meet FCC emission limits. Proper cables are available from IBM authorized dealers. IBM is not responsible for any radio or television interference caused by using other than recommended cables or by unauthorized modifications to this equipment. It is the responsibility of the user to correct such interference. CAUTION: This product is equipped with a 3-wire power cord and plug for the user's safety. Use this power cord in conjunction with a properly grounded electrical outlet to avoid electrical shock. Third Edition (June 1988) Thismajor revision obsoletes previous editions of the IBM RT PC User Setup Guide.
    [Show full text]
  • Proceedings of the Rexx Symposium for Developers and Users
    SLAC-R-95-464 CONF-9505198-- PROCEEDINGS OF THE REXX SYMPOSIUM FOR DEVELOPERS AND USERS May 1-3,1995 Stanford, California Convened by STANFORD LINEAR ACCELERATOR CENTER STANFORD UNIVERSITY, STANFORD, CALIFORNIA 94309 Program Committee Cathie Dager of SLAC, Convener Forrest Garnett of IBM Pam Taylor of The Workstation Group James Weissman Prepared for the Department of Energy under Contract number DE-AC03-76SF00515 Printed in the United States of America. Available from the National Technical Information Service, U.S. Department of Commerce, 5285 Port Royal Road, Springfield, Virginia 22161. DISTRIBUTION OF THIS DOCUMENT IS UNLIMITED ;--. i*-„r> ->&• DISCLAIMER This report was prepared as an account of work sponsored by an agency of the United States Government. Neither the United States Government nor any agency thereof, nor any of their employees, make any warranty, express or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or usefulness of any information, apparatus, product, or process disclosed, or represents that its use would not infringe privately owned rights. Reference herein to any specific commercial product, process, or service by trade name, trademark, manufacturer, or otherwise does not necessarily constitute or imply its endorsement, recommendation, or favoring by the United States Government or any agency thereof. The views and opinions of authors expressed herein do not necessarily state or reflect those of the United States Government or any agency thereof. DISCLAIMER Portions
    [Show full text]
  • Z/OS Resilience Enhancements
    17118: z/OS Resilience Enhancements Harry Yudenfriend IBM Fellow, Storage Development March 3, 2015 Insert Custom Session QR if Desired. Agenda • Review strategy for improving SAN resilience • Details of z/OS 1.13 Enhancements • Enhancements for 2014 Session 16896: IBM z13 and DS8870 I/O Innovations for z Systems for additional information on z/OS resilience enhancements. © 2015 IBM Corporation 3 SAN Resilience Strategy • Clients should consider exploiting technologies to improve SAN resilience – Quick detection of errors – First failure data capture – Automatically identify route cause and failing component – Minimize impact on production work by fencing the failing resources quickly – Prevent errors from impacting production work by identifying problem links © 2015 IBM Corporation 4 FICON Enterprise QoS • Tight timeouts for quicker recognition of lost frames and more responsive recovery • Differentiate between lost frames and congestion • Explicit notification of SAN fabric issues • End-to-End Data integrity checking transparent to applications and middleware • In-band instrumentation to enable – SAN health checks – Smart channel path selection – Work Load Management – Autonomic identification of faulty SAN components with Purge-Path-Extended – Capacity planning – Problem determination – Identification of Single Points of Failure – Real time configuration checking with reset event and self description • No partially updated records in the presence of a failure • Proactive identification of faulty links via Link Incident Reporting • Integrated management software for safe switching for z/OS and storage • High Integrity, High Security Fabric © 2015 IBM Corporation 5 System z Technology Summary • Pre-2013 Items a) IOS Recovery option: RECOVERY,LIMITED_RECTIME b) z/OS 1.13 I/O error thresholds and recovery aggregation c) z/OS message to identify failing link based on LESB data d) HCD Generation of CONFIGxx member with D M=CONFIG(xx) e) Purge Path Extended (LESB data to SYS1.LOGREC) f) zHPF Read Exchange Concise g) CMR time to differentiate between congestion vs.
    [Show full text]
  • John Backus (1924–2007) Inventor of Science’S Most Widespread Programming Language, Fortran
    NEWS & VIEWS NATURE|Vol 446|26 April 2007 OBITUARY John Backus (1924–2007) Inventor of science’s most widespread programming language, Fortran. John Backus, who died on 17 March, was developed elsewhere around the same time, a pioneer in the early development of however, Speedcoding produced programs IBM/AP computer programming languages, and was that were uneconomically slow. subsequently a leading researcher in so- Backus proposed to his manager the called functional programming. He spent his development of a system he called the entire career with IBM. Formula Translator — later contracted to Backus was born on 3 December 1924 in Fortran — in autumn 1953 for the model Philadelphia, and was raised in Wilmington, 704 computer, which was soon to be Delaware. His father had been trained as a launched. The unique feature of Fortran was chemist, but changed careers to become a that it would produce programs that were partner in a brokerage house, and the family 90% as good as those written by a human became wealthy and socially prominent. As a programmer. Backus got the go-ahead, and child, Backus enjoyed mechanical tinkering was allocated a team of ten programmers and loved his chemistry set, but showed for six months. Designing a translator that little scholastic interest or aptitude. He was produced efficient programs turned out to be sent to The Hill School, an exclusive private a huge challenge, and, by the time the system high school in Pottstown, Pennsylvania. was launched in April 1957, six months had His academic performance was so poor that become three years.
    [Show full text]
  • RISC Architecture
    REDUCED INSTRUCTION SET COMPUTERS Prof. Vojin G. Oklobdzija Integration Berkeley, CA 94708 Keywords: IBM 801; RISC; computer architecture; Load/Store Architecture; instruction sets; pipelining; super-scalar machines; super-pipeline machines; optimizing compiler; Branch and Execute; Delayed Branch; Cache; Harvard Architecture; Delayed Load; Super-Scalar; Super-Pipelined. Fall 1999 1. ARCHITECTURE The term Computer Architecture was first defined in the paper by Amdahl, Blaauw and Brooks of International Business Machines (IBM) Corporation announcing IBM System/360 computer family on April 7, 1964 [1,17]. On that day IBM Corporation introduced, in the words of IBM spokesman, "the most important product announcement that this corporation has made in its history". Computer architecture was defined as the attributes of a computer seen by the machine language programmer as described in the Principles of Operation. IBM referred to the Principles of Operation as a definition of the machine which enables machine language programmer to write functionally correct, time independent programs that would run across a number of implementations of that particular architecture. The architecture specification covers: all functions of the machine that are observable by the program [2]. On the other hand Principles of Operation. are used to define the functions that the implementation should provide. In order to be functionally correct it is necessary that the implementation conforms to the Principles of Operation. Principles of Operation document defines computer architecture which includes: • Instruction set • Instruction format • Operation codes • Addressing modes • All registers and memory locations that may be directly manipulated or tested by a machine language program • Formats for data representation Machine Implementation was defined as the actual system organization and hardware structure encompassing the major functional units, data paths, and control.
    [Show full text]
  • Speaker Bios
    SPEAKER BIOS Speaker: Nilanjan Banerjee, Associate Professor, Computer Science & Electrical Engineering, UMBC Topic: Internet of Things/Cyber-Physical Systems Nilanjan Banerjee is an Associate Professor at University of Maryland, Baltimore County. He is an expert in mobile and sensor systems with focus on designing end-to-end cyber-physical systems with applications to physical rehabilitation, physiological monitoring, and home energy management systems. He holds a Ph.D. and a M.S. in Computer Science from the University of Massachusetts Amherst and a BTech. (Hons.) from Indian Institute of Technology, Kharagpur. Speaker: Keith Bowman, Dean, College of Engineering & Information Technology (COEIT), UMBC Topics: Welcoming Remarks and Farewell and Wrap Keith J. Bowman has begun his tenure as the new dean of UMBC’s College of Engineering and Information Technology (COEIT). He joined UMBC on August 1, 2017, from San Francisco State University in California, where he served as dean of the College of Science and Engineering since 2015. Bowman holds a Ph.D. in materials science from the University of Michigan, and B.S. and M.S. degrees in materials science from Case Western Reserve University. Prior to his role at SFSU, he held various positions at the Illinois Institute of Technology and Purdue University. At the Illinois Institute of Technology, he was the Duchossois Leadership Professor and chair of mechanical, materials, and aerospace engineering. In Purdue University’s School of Materials Engineering, he served as a professor and head of the school. He also held visiting professorships at the Technical University of Darmstadt in Germany and at the University of New South Wales in Australia.
    [Show full text]
  • 2 9215FQ14 FREQUENTLY ASKED QUESTIONS Category Pages Facilities & Buildings 3-10 General Reference 11-20 Human Resources
    2 FREQUENTLY ASKED QUESTIONS Category Pages Facilities & Buildings 3-10 General Reference 11-20 Human Resources 21-22 Legal 23-25 Marketing 26 Personal Names (Individuals) 27 Predecessor Companies 28-29 Products & Services 30-89 Public Relations 90 Research 91-97 April 10, 2007 9215FQ14 3 Facilities & Buildings Q. When did IBM first open its offices in my town? A. While it is not possible for us to provide such information for each and every office facility throughout the world, the following listing provides the date IBM offices were established in more than 300 U.S. and international locations: Adelaide, Australia 1914 Akron, Ohio 1917 Albany, New York 1919 Albuquerque, New Mexico 1940 Alexandria, Egypt 1934 Algiers, Algeria 1932 Altoona, Pennsylvania 1915 Amsterdam, Netherlands 1914 Anchorage, Alaska 1947 Ankara, Turkey 1935 Asheville, North Carolina 1946 Asuncion, Paraguay 1941 Athens, Greece 1935 Atlanta, Georgia 1914 Aurora, Illinois 1946 Austin, Texas 1937 Baghdad, Iraq 1947 Baltimore, Maryland 1915 Bangor, Maine 1946 Barcelona, Spain 1923 Barranquilla, Colombia 1946 Baton Rouge, Louisiana 1938 Beaumont, Texas 1946 Belgrade, Yugoslavia 1926 Belo Horizonte, Brazil 1934 Bergen, Norway 1946 Berlin, Germany 1914 (prior to) Bethlehem, Pennsylvania 1938 Beyrouth, Lebanon 1947 Bilbao, Spain 1946 Birmingham, Alabama 1919 Birmingham, England 1930 Bogota, Colombia 1931 Boise, Idaho 1948 Bordeaux, France 1932 Boston, Massachusetts 1914 Brantford, Ontario 1947 Bremen, Germany 1938 9215FQ14 4 Bridgeport, Connecticut 1919 Brisbane, Australia
    [Show full text]
  • The Multiple Precision Integers and Rationals Library Edition 1.0
    MPIR The Multiple Precision Integers and Rationals Library Edition 1.0 8 April 2009 This manual describes how to install and use MPIR, the Multiple Precision Integers and Ratio- nals library, version 1.0. Copyright 1991, 1993, 1994, 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006 Free Software Foundation, Inc. Copyright 2008 William Hart Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, with the Front-Cover Texts being \A GNU Manual", and with the Back-Cover Texts being \You have freedom to copy and modify this GNU Manual, like GNU software". A copy of the license is included in Appendix C [GNU Free Documentation License], page 121. i Table of Contents MPIR Copying Conditions ................................. 1 1 Introduction to MPIR .................................. 2 1.1 How to use this Manual ........................................................ 2 2 Installing MPIR........................................ 3 2.1 Build Options ................................................................. 3 2.2 ABI and ISA.................................................................. 8 2.3 Notes for Package Builds ...................................................... 11 2.4 Notes for Particular Systems .................................................. 12 2.5 Known Build Problems ....................................................... 14 2.6
    [Show full text]
  • Modern Database Systems: Newsql, Nosql and Modernized Classic Systems
    NetApp 7th Annual University Day NetApp HQ, Sunnyvale, CA, USA 17 February 2014 Modern Database Systems: NewSQL, NoSQL and Modernized Classic Systems C. Mohan IBM Fellow and Former IBM India Chief Scientist IBM Almaden Research Center, San Jose, CA 95120, USA [email protected] http://bit.ly/CMohan Talk Version of Tutorial Presented First at 39th International Conference on Very Large Data Bases (VLDB) Riva del Garda, Italy, 29 August 2013 Links to Revised Tutorial Slides and Bibliography at http://bit.ly/CMnMDS Background + Warnings § My personal opinions, NOT necessarily IBM’s positions/opinions § Lots of hype on NoSQL (lesser on NewSQL) in industry, academia & VC world – this Kool-Aid has intoxicated many J § Been a details oriented, hard core DB person for > 3 decades – I go beyond hype, am not easily swayed by the latest fashion! § Not a relational bigot – most of my results on systems topics have applied to all sorts of persistent, distributed information systems § Have dissected many IBM and non-IBM systems’ internals (including pre- and post-relational ones) § Don’t claim to have all the answers or make definitive assertions § Aim: not exhaustive survey of modern systems or details of too many specific systems – broad brush analysis of good (sensible) and bad (nonsenSQL) of NoSQL/NewSQL, warn of pitfalls – time to pause and introspect. Give a few systems’ interesting details. § NOT against NoSQL but unhappy with choices on internals, design justifications (“anything goes”), and not learning enough from the past C. Mohan, MDS Tutorial,
    [Show full text]
  • Application Servers and Associated Technologies
    ACM SIGMOD International Conference on Management of Data (SIGMOD'02), Madison, USA, June 2002 Tutorial: Application Servers and Associated Technologies C. MOHAN IBM Fellow [email protected] http://www.almaden.ibm.com/u/mohan/ IBM Almaden Research Center 650 Harry Road, K01/B1 San Jose, CA 95120 USA These slides are available at http://www.almaden.ibm.com/u/mohan/AppServersTutorial_SIGMOD2002_Slides.pdf App Servers, Mohan 1 SIGMOD2002, Madison, 6/2002 About the Speaker Dr. C. Mohan joined the IBM Almaden Research Center as a Research Staff Member in 1981. In 1997, he was named an IBM Fellow for being recognized worldwide as a leading innovator in transaction management. He received the ACM SIGMOD Innovations Award in 1996 in recognition of his innovative contributions to the development and use of database systems. At VLDB99, he was honored with the 10 Year Best Paper Award for the impact of his work on the ARIES family of algorithms. In 1992, he was elected to the IBM Academy of Technology. Mohan is a core member of IBM's Application Integration Middleware (AIM) Architecture Board. Currently, he is working on data caching and next generation messaging in the context of WebSphere and DB2. He was the founding leader of the Dominotes project which resulted in the enhancement of Domino/Notes's scalability by the introduction of transactional recovery in R5. Prior to that, Mohan led the Exotica project which was focussed on the workflow product FlowMark (now called MQSeries Workflow), the messaging product MQSeries and the groupware product Lotus Notes. Mohan was a designer/implementer of the R* distributed DBMS, the Starburst extensible DBMS and DB2.
    [Show full text]
  • Introduction a Brief History of Computing
    CSE 322 — COMPUTER ARCHITECTURE II Introduction A Brief History Of Computing January 18, 2000–7 CSE 322 — COMPUTER ARCHITECTURE II Some Basic Terms Architecture: “The art or science of building habitable structures” Our Structures: Computer Systems Our Inhabitants: Computer programs Computer Architecture: Art of describing and building computer systems which can execute computer programs; alternatively: structure & behavior of computer as seen by assembly level programmer Computer Organization: Description of major logical & physical components of a computer and how they interact Computer Implementation: Description of electrical components used to build a computer Computer Execution Model: Description of how programs execute within a computer architecture Instruction Set Architecture (ISA): Description of the instructions which can make up a computer program, and the semantics of what each does when executed Feature Size (in microns): minimum width of a gate of a CMOS transistor possible in a particular technology generation A Brief History Of Computing January 18, 2000–8 CSE 322 — COMPUTER ARCHITECTURE II People & the Computer Design Process Computer Architect: Architecture Level • Develops ISA, computer system architecture • Interplay between hardware (machine organization) and software (compilers, interpreters, runtime) needed to sustain the “inhabitants” Computer Designer: Organization Level • Develops detailed machine organization - Partitioning into major blocks - Specification of each block’s interfaces & functionality - Selects
    [Show full text]
  • Chapter 17 Structural Dynamics Research Corporation
    Chapter 17 Structural Dynamics Research Corporation Structural Dynamics Research Corporation (SDRC) was founded in 1967 by Dr. Jason (Jack) Lemon, Albert Peter, Robert Farell, Jim Sherlock and several others. Lemon and his partners had previously held teaching and research positions in the University of Cincinnati’s Mechanical Engineering Department. Initially, this was a mechanical engineering consulting company that over the years made the transition to being a full- fledged mechanical design software company. One of the company’s early consulting assignments was for U. S. Steel and it was so impressed by the work SDRC did that it decided to invest in the company and for a time held about a 40 percent ownership position. The relationship with U.S. Steel was far more than simply a financial investment. SDRC’s engineers worked closely with U. S. Steel’s sales and marketing people to create new markets for steel. One example was the machine tool industry which had traditionally used castings for the base of their machine tools. U.S. Steel wanted to sell these companies plate steel that could be welded into the shapes needed. SDRC’s engineers developed the analytical techniques that proved to these prospective customers that the steel plate bases were an acceptable alternative. This relationship generated numerous leads for SDRC’s seminars on advanced engineering design and analysis technologies. U.S. Steel also had two people on the company’s board of directors during this period. Dr. Russ Henke, who was also a University of Cincinnati graduate, joined SDRC in 1969 as director of computer operations, at a time when the company had about 20 employees.
    [Show full text]