DOCSLIB.ORG

The PORTHOS Executive System for the IBM 7094

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
The PORTHOS Executive System for the IBM 7094 A § 1 " * '& I m I ^ ;/ 1 ^ # **W : : : The Porthos Executive System for the IBM 7O9I+ User ' s Manual Table of Contents Title Sheet Preface Table of Contents 1. The 709^-1^01 Computer Installation 1.1. Description 1.1.1. General 1.1.2. Organization 1.1.3* Equipment 1.2. Programming Services 1.2.1. System Consulting 1.2.2. System Development 1.2.3- Associated Programmers 1.3« Library Services 1.3* 1' Program Documentation 1.3*2. Subroutines I.3. 3« Reference Publications 1.3.1+. The Mailing List 1.3' 5* Information Bulletins Date 5/1/65 Section Contents Page: 1 Change 2 Porthos Manual Digitized by the Internet Archive in 2012 with funding from University of Illinois Urbana-Champaign http://archive.org/details/porthosexecutivesyOOuniv : s 2. Use of the Computing Facility 2.1. Conditions of Use 2.1.1. Policy for Charging for Computer Use 2.1.2. Refunding of IBM 7094 Time Due to System or Machine Failures 2.1.2.1. In-System Jobs 2.1.2.2. Relinquish Jobs 2.2. Application for Use of Equipment 2.2.1. The Form 2.2.2. Submission and Approval 2.2.3. Entries on the Problem Specification Form 2.2.4. Changes in the Problem Specification 2.2.5. Problem Abstracts 2.3- Logging and Control of Computer Time 2.3«1« Accounting for Computer Time 2.3.2. Notices to Users Concerning Lapsing Time 2.3.3. Department Reports 2.3'3-l« Internal Reports 2. 3- 3* 2. The Technical Progress Report 2. 3- 3» 3* Departmental Monthly Statements 2.3.3-4. Billing 2.4. Supplies 2.4.1. Expendable Supplies 2.4.2. Non- expendable Supplies Date: 5/1/65 Section: Contents Page: 2 Change 2 Port ho Manual : : 3. Automatic Processing of Programs 3.1- General 3.2. The PORTHOS Executive System 3.2.1. Introduction 3-2.2. Programming Conventions of the System 3.2.3. The Executive System Monitor 3.2.4. The System Loader 3-2.4.1. Introduction: Relocatable Programs 3-2.4.2. COMMON, PROGRAM COMMON, and ERASABLE 3.2.4.3. The Core Constant 3.2.4.4. The Transfer Vector 3.2.4.5. Program Cards 3.2.4.6. The Loader Map 3.2.4.7. Ping-Pong 3.2.4.8. Relocation of Programs 3.2.4.9. Column-Binary Card Formats 3.2.4.9.1. General 3.2.4.9.2. Program Card 3.2.4.9.3. Relocatable Instruction Card 3.2.4.9.4. Binary Transition Card 3-2.4.10. Loading Block Description 3.2.4.11. SPLIT CORE LOADING 3.2.4.12. SUBTRACE 3.2.4.13. Missing Subroutine Procedure 3.2.4.14. Routine to SAVE CORE 3-2.4.15. Use of Loader During Execution 3.2.5. Low Core System Control 3.2.5.1. Introduction 3.2.5.2. Machine Terminology 3.2.5.3. Description of the Standard 7094 Trap 3.2.5.4. Machine Status and Trap Programming 3.2.5.5. Core Storage Clock 3.2.5.5.I. Description of Equipment 3.2.5.6. Protection Mode (Memory Protect) Date 5/1/65 Section: Contents Page: 3 ' Change 2 Porthos Manual : 3.2. 5* 7* Input/Output Programming 3« 2.5. 7* 1. Description of Equipment 3.2.5'7.2. Main Frame Instructions 3.2.5.7.3. Channel Commands 3.2.5.7.^. Parity Checking and Redundancy on Tapes 3.2.5.7.5. Data Selects and Non-data Selects 3.2.5.7.6. Channel Trap Control 3.2.5.7.7. Select Routines 3.2.5.7.8. The Channel Trap Processor 3.2.5.7.9. Special Tape Handling Routines 3.2.5.7.10. Peripheral Tape Buffering Routines 3.2.5.8. Floating Point Trap 3.2.5.8.1. General 3.2.5.8.2. System Floating Point Trap Procedure 3.2.5.9. Action of the I/O Routines at End-of-File 3.2.5.10. System Exit Routines 3.2.5.11. Miscellaneous Routines 3.3. Programming Systems in PORTHOS 3.3.1. General 3.3.1.1. Machine-Oriented Languages 3.3.1.2. Procedure-Oriented Languages 3.3.1.3. Problem-Oriented Languages 3»3«1.^. Specialized Programs 3.3.2. Machine-Oriented Languages in PORTHOS 3.3.2.1. SCAT 3.3.2.2. SCATRE 3.3.2.3. SPS/90-Assembler for 1^01 Programs on the 7O9U 3.3.2.3.1. Origin and Purpose 3.3.2.3.2. SPS/90 Source Language 3.3.2.3.3. Usage 3.3.3. Procedure-Oriented Languages in PORTHOS 3.3.3.I. General Discussion of Available Systems 3.3.3.1.1. Introduction 3.3.3.1.2. Compilation Speed 3.3.3.1.3. Error Checking 3.3.3.1.^. Object Program Efficiency Date: 5/1/65 Section: Contents Page: k j Change 2 Porthos Manual : : s 3«3«3«1'5« Advantages of the Various Compilers 3«3»3«1«6. Disadvantages of the Various Compilers 3.3.3.2. FORTRAN II (or FASTRAN) 3.3.3-2.1. General 3.3.3.2.2. FAP, the FORTRAN II Assembly Program 3.3.3.2.3. The FORTRAN Monitor, IBSYS, and the SHARE Operating System (SOS) 3.3.3.2.4. Modifications to FASTRAN and FORTRAN II within PORTHOS 3.3.3.2.5. Differences between FASTRAN and FORTRAN IBM 3.3.3.2.6. FORTRAN Errors Detected and Processed by FASTRAN 3.3.3.2.7. Additional Features of FASTRAN 3.3.3.3. ALGOL-60 3.3.3.3.1. General 3.3.3.3.2. References 3.3.3.3.3. The ALGOL Algorithm Index 3.3.3.4. MAD 3.3.3.4.1. General 3.3.3.4.2. References 3.3.4. Specialized Programming Systems 3.3.4.1. The Statistical Monitor (STATMON) 3.3-4.1.1. General 3.3.4.1.2. General Functions 3.3.4.1.3. Basic Matrix Operations 3.3-4.2. The IBM 65O Simulator (SIM 650) 3.3.4.3. SNOBOL 3.3.4.3.1. Introduction 3.3.4.3.2. Basic Concepts of SNOBOL 3.3.4.3.3. Structure of a SNOBOL Program 3.3.4.3.4. Arithmetic Operations on Strings 3.3.4.3.5. Indirectness 3.3.4.3.6. Input-Output of Strings Date: 5/1/65 Section: Contents Page 5 Change 2 Port ho Manual : : 3-3.4.3.7 Scanning Algorithm 3-3.4.3.8 Sample Programs 3- 3.^-3-9 Additional Information for SNOBOL Users 3-3.4.4. ipl-v 3-3.4.4.1 Introduction 3.3.4.4.2. The IPL-V Translator 3.3.4.4.3. IPL-V Symbolic Deck 3.3.4.4.4. Internal IPL-V Coding 3.3.4.4.5. IPL-V Tape Structure 3.3.4.4.6. Monitor Control Points 3- 3* 4. 4.7* Output Carriage Controls 3.3.4.4.8. Printing via ' J15n' Primitives 3.3-4.4,9. New and Missing Primitives 3.3.4.4.10. Automatic Buffer Feature 3.3.4.4.11. Save for Restart and Reloading 3« 3*4. 4. 12. Inprocess Loading 3.3.4.4.13. Arithmetic Processes 3.3.4.4.14. Binary Primitive 3.3.4.4.15. Post Mortem 3.3.4.4.16. Error and Listing Comments 3.3.4.5. LPG1 3.3.4.5.1. Introduction 3.3.4.5.2. Statement of Problem 3.3.4.5.3. Standard Procedure 3.3.4.5.4. General Procedure 3.3.4.5.5. LPG1 Examples 3.3.4.5.6. LPG1 and LP-90 Differences 3.4. Summary of Available Publications Pertaining to PORTHOS and its Parts Date: 5/1/65 Section Contents Page: 6 Change 2 Porthos Manual I-. Running a Job on the 7094 4.1. General 4.2. Jobs Run Under System Control 1+.2.1. General 4.2.2. Preparing the Job 4.2.2.1. The Problem Run Card 4.2.2.2. The Comments Cards-When Required 4.2.2.3. The Control Cards 4.2.2.3-1. General 4.2.2.3.2. Identification of Binary Cards 4.2.2.3.3. Translator Selection 4.2.2.3.4. Binary Cards as Input 4.2.2.3.5. Punch Binary Cards 4.2.2.3.6. Data 4.2.2.3.7. Program Execution 4.2.2.3.8. Program Development Aids 4.2.2.3.9. The Control Card for Multiple-Core Jobs 4.2.2.3.10. The $ REM0VE TAPES Control Card 4.2.2.3.11. The $ SUBTRACE Control Card 4.2.2.3.12. $ Control Card Summary 4.2.2.4. Arrangement of the Input Deck 4.2.2.5. Listing and Reproducing Cards and Tapes 4.2.2.6. Use of the Cathode Ray Tube Display (CRT) 4.2.2.6.1. General 4.2.2.6.2. Operation 4.2.2.6.3. Coordinate Display 4.2.2.6.4. Recording Unit 4.2.2.6.5. Plotting 4.2.2.6.6. Display Unit 4.2.2.6.7. Camera and its Associated Equipment 4.2.2.6.8. Procedure for Use of the CRT Date: 5/1/65 Section: Contents Page : 7 Change : 2 Port ho s Manual : : s 5. The Subroutine Library 5.1. General 5.2. SHARE Routine Classification Scheme 5»3« Library Subroutines 5.3«1« Documentation 5* 3* 2.
Load more

Recommended publications
  • IBM 1401 System Summary
    File No. 1401-00 Form A24-1401-1 Systems Reference Library IBM 1401 System Summary This reference publication contains brief descriptions of the machine features, components, configurations, and special features. Also included is a section on pro­ grams and programming systems. Publications providing detailed information on sub­ jects discussed in this summary are listed in IB~I 1401 and 1460 Bibliography, Form A24-1495. Major Revision (September 1964) This publication, Form A24-1401-1, is a major revision of and obsoletes Form A24-1401-0. Significant changes have been made throughout the publication. Reprinted April 1966 Copies of this and other IBM publications can be obtained through IBM Branch Offices. Address comments concerning the content of this publication to IBM Product Publications, Endicott, New York 13764. Contents IBM 1401 System Summary . ........... 5 System Concepts . ................ 6 Card-Oriented System .... ......... 11 Physical Features. 11 Interleaving. .. .................................... 14 Data Flow.... ... ... ... ... .. ... ... .. ................... 14 Checking ................................................... 15 Word Mark.. ... ... ... ... ... ... .. ... ... ... ........... 15 Stored-Program Instructions. .................. 15 Operation Codes . .. 18 Editing. .. ............ 18 IBM 1401 Console ............................................ 19 IBM 1406 Storage Unit. ........................... 20 Magnetic-Tape-Oriented System . ........................... 22 Data Flow .................................................
    [Show full text]
  • Ibm Presentations: Black Template
    Zorislav Sic, Power Systems SME, IBM CEE May 2009 IBM Dynamic Infrastructure FORUM Effective Workload Consolidation on Power © 2009 IBM Corporation Building a smarter planet The difference betweenGlobally, white systems and white and templates infrastructure lies are in the intended audiencereaching and a usagebreaking point. Proliferation of servers and networking devices . Excessive energy usage and heating problems . Inadequate power and cooling infrastructure . Data silos and data synchronization . Expectations that “everything” is connected . Linear staffing costs . Skyrocketing software costs . Unexplained outages Meanwhile, customer expectations, competitive pressures, regulatory requirements and fiscal pressures are increasing. 2 © 2009 IBM Corporation Building a smarter planet IT Leaders Need to do More With Less Operational issues can inhibit business growth and innovation CIO key spending initiatives Overburdened IT Server virtualization staff 53% Server consolidation 44% Cost cutting 42% Application integration 37% Data center consolidation 36% Business intelligence Complex service 33% Security delivery 28% Storage hardware 26% Disaster recovery 25% Storage virtualization 23% 0% 10% 20% 30% 40% 50% 60% % of respondents rating issue as high priority Strained IT budgets Source: Goldman Sachs Group IT Spending Survey, July 2008 © 2009 IBM Corporation Building a smarter planet A dynamic infrastructure addresses today’s challenges… and tomorrow’s opportunities REDUCE COST Not just containing operational cost and complexity, but achieving breakthrough productivity gains through virtualization, optimization, energy stewardship, and flexible sourcing. IMPROVE SERVICE Not only ensuring high availability and quality of existing services, but also meeting customer expectations for real-time, dynamic access to innovative new services. MANAGE RISK Not only addressing today’s security, resiliency, and compliance challenges, but also preparing for the new risks posed by an even more connected and collaborative world.
    [Show full text]
  • PC Hardware Contents
    PC Hardware Contents 1 Computer hardware 1 1.1 Von Neumann architecture ...................................... 1 1.2 Sales .................................................. 1 1.3 Different systems ........................................... 2 1.3.1 Personal computer ...................................... 2 1.3.2 Mainframe computer ..................................... 3 1.3.3 Departmental computing ................................... 4 1.3.4 Supercomputer ........................................ 4 1.4 See also ................................................ 4 1.5 References ............................................... 4 1.6 External links ............................................. 4 2 Central processing unit 5 2.1 History ................................................. 5 2.1.1 Transistor and integrated circuit CPUs ............................ 6 2.1.2 Microprocessors ....................................... 7 2.2 Operation ............................................... 8 2.2.1 Fetch ............................................. 8 2.2.2 Decode ............................................ 8 2.2.3 Execute ............................................ 9 2.3 Design and implementation ...................................... 9 2.3.1 Control unit .......................................... 9 2.3.2 Arithmetic logic unit ..................................... 9 2.3.3 Integer range ......................................... 10 2.3.4 Clock rate ........................................... 10 2.3.5 Parallelism .........................................
    [Show full text]
  • History of Operating Systems
    System Architecture History of Operating Systems Some slides from A. D. Joseph, University of Berkeley See also: www.osdata.com/kind/history.htm www.armory.com/~spectre/tech.html courses.cs.vt.edu/~cs1104/VirtualMachines/OS.1.html en.wikipedia.org/wiki/History_of_operating_systems © 2008 Universität Karlsruhe (TH), System Architecture Group 1 Moore’s Law Drives OS Change 1981 2006 Factor CPU MHz, 10 3200x4 1,280 Cycles/inst 3—10 0.25—0.5 6—40 DRAM capacity 128KB 4GB 32,768 Disk capacity 10MB 1TB 100, 000 Net bandwidth 9600 b/s 1 Gb/s 110,000 # addr bits 16 32 2 #users/machine 10 1 0.1 Price $25,000 $4,000 0.2 Typical academic computer 1981 vs 2006 © 2008 Universität Karlsruhe (TH), System Architecture Group 2 Moore’s Law Effects Nothing like this in any other area of business Transportation in over 200 years: Only 2 orders of magnitude from horseback @10mph to Concorde @1000mph Computers do this every decade What does this mean for us? Techniques have to vary over time to adapt to changing tradeoffs Let’s place a lot more emphasis on principles The key concepts underlying computer systems Less emphasis on facts that are likely to change over the next few years… Let’s examine the way changes in $/MIP has radically changed how OS’s work © 2008 Universität Karlsruhe (TH), System Architecture Group 3 Dawn of Time ENIAC: (1945-55) “The machine designed by Eckert and Mauchly was a monstrosity. When it was finished, the ENIAC filled an entire room, weighed 30 tons, and consumed 200 kilowatts of power.” http://ei.cs.vt.edu/~history/ENIAC.Richey.HTML © 2008 Universität Karlsruhe (TH), System Architecture Group 4 History Phase 1: 19481948--7070 Expensive Hardware Cheap Humans © 2008 Universität Karlsruhe (TH), System Architecture Group 5 History of Systems History OS: Evolution Step 0 APP OS Hardware Simple OS: One program, one user, one machine: examples: early computers, early PCs, embedded controllers such as Nintendo, cars, elevators OS just a library of standard services, e.g.
    [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]
  • IBM 709 MANUFACTU RER IBM 709 Data Processing System International Business Machines Corporation
    IBM 709 MANUFACTU RER IBM 709 Data Processing System International Business Machines Corporation Photo by International Business Machines Corporation at Point Mugu, California and one at Point Arguello, APPLICATIONS California. Land Air is the lessee, and our major Manufacturer committment is for missile test flight data reduction. This is a general purpose computer doing both scien­ In addition, we provide computing facilities for the tific computing and commercial work. The system is entire installation at Mugu (general scientific and scientifically oriented with fast internal speeds. engineering research and data processing). USA Ballistic Missile Agency Redstone Arsenal U.S.N. Pacific Missile Range Ft. Mugu Located at Computation Laboratory, Redstone Arsenal, Operated by Land Air, Inc. ALabama, the system is used for scientific and commer­ Located at the Naval Missile Faculty, Point Arguello, cial applications. California, the system is used on the main problem U. S. Army Electronic Proving Ground of range safety impact predicition in real time using Located in Greely Hall, Fort Huachuca, Arizona, sys­ FPS-l6 Radar and Cubic COTAR data. System is also tem is used in support of the tactical field army used for post flight trajectory reduction of FPS-l6 and the technical program of the departments of the radar data and for trajectory integration and analysis, U. S. Army Electronic Proving Ground. etc. U.S.N. Pacific Missile Range Ft. Mugu USN OTS China Lake, California Operated by Land Air, Inc. Located at the Data Computation Branch, Assessment Located at the Pacific Missile Range, Point Mugu, the DiVision, Test Department, the computer is used for system is used for the processing of missile test data reduction and scientific computation as related data (radar, optical, and telemetry), for real time to Naval Ordnance, Test, Development & Research applications, and for the solution of general mathe­ (l5% of computer time devoted to management data pro­ m.atical problems.
    [Show full text]
  • The Architecture of IBM's Early Computers
    C. J. Bashe W. Buchholz G. V. Hawkins J. J. lngram N. Rochester The Architectureof IBM’s Early Computers Most of the early computers made by IBM for commercial productionare briefly described with an emphasis on archi- tecture and performance. The description covers a period offifteen years, starting with the design of an experimental machine in 1W9 and extending to, but not including, the announcement in 1964 of Systeml360. Introduction This is a technical account of IBM’s principal computers Table 1 illustrates the chronology of the machines dis- during the fifteen-year period beginning in late 1949 and cussed in this paper. The membersof a family or series of leading up to the announcement in 1964 of Systeml360. machines appear vertically in a column; the later entries They wereall electronic stored-program computers. Each are more or less upward compatible with earlier ones. had a random-access memory that was reasonably large (There is nofamily relationship, however, among thema- by the standards of the time, could do arithmetic and chines in the column labeled “Others.”) All machines up logic, could call subroutines, could-and did-translate to 1957 used vacuum-tube electronics; from 1958 on, all from various symbolic languages to its own machine lan- of IBM’s computers were built with transistors. Every guage, and eachhad a substantial setof input/output (I/O) machine listed is discussed orreferred to in the text. equipment. This accountemphasizes architecture and performance, that is, the programmer’s view at the level Except for a discussion of IBM’s precursor machines, of machine language.
    [Show full text]
  • The Discursive Coding of Software: a Study of the Relationship Between Stability and Change Jennifer Helene Maher Iowa State University
    View metadata, citation and similar papers at core.ac.uk brought to you by CORE provided by Digital Repository @ Iowa State University Iowa State University Capstones, Theses and Retrospective Theses and Dissertations Dissertations 2006 The discursive coding of software: a study of the relationship between stability and change Jennifer Helene Maher Iowa State University Follow this and additional works at: https://lib.dr.iastate.edu/rtd Part of the Discourse and Text Linguistics Commons, Other Communication Commons, Programming Languages and Compilers Commons, and the Rhetoric and Composition Commons Recommended Citation Maher, Jennifer Helene, "The discursive coding of software: a study of the relationship between stability and change" (2006). Retrospective Theses and Dissertations. 13941. https://lib.dr.iastate.edu/rtd/13941 This Dissertation is brought to you for free and open access by the Iowa State University Capstones, Theses and Dissertations at Iowa State University Digital Repository. It has been accepted for inclusion in Retrospective Theses and Dissertations by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. The discursive coding of software: A study of the relationship between stability and change by Jennifer Helene Maher A dissertation submitted to the graduate faculty in partial fulfillment of the requirements for the degree of DOCTOR OF PHILOSOPHY Major: Rhetoric and Professional Communication Program of Study Committee: David Russell, Major Professor Carl Herndl Dorothy Winsor Diane Price Herndl David Schweingruber Iowa State University Ames, Iowa 2006 Copyright © Jennifer Helene Maher, 2006. All rights reserved UMI Number: 3243534 UMI Microform 3243534 Copyright 2007 by ProQuest Information and Learning Company.
    [Show full text]
  • Background Analysis and Design of ABOS, an Agent-Based Operating System
    Background Analysis and Design of ABOS, an Agent-Based Operating System Author: Mikael Svahnberg, [email protected] A Software Engineering Master’s Thesis at the University of Karlskrona/Ronneby, 1998. Abstract Modern operating systems should be extensible and flexible. This means that the operating system should be able to accept new behaviour and change existing behaviour without too much trouble and that it should ideally also be able to do this without any, or very little, downtime. Furthermore, during the past years the importance of the network has increased drastically, creating a demand for operating systems to function in a distributed environment. To achieve this flexibility and distribut- edness, I have designed and evaluated ABOS, an Agent-Based Operating System. ABOS uses agents to solve all the tasks of the operating system kernel, thus moving away from traditional monolithic kernel structures. Early results show that I have gained in flexibility and modularity, cre- ating a fault-tolerant distributed operating system that can adapt and be adapted to almost any situa- tion with negligible decrease in performance. Within ABOS some tasks has been designed further, and there exists a demonstration of how the agent-based filesystem might work. Keywords: Operating systems, Practical application of multi-agent systems Author Mikael Svahnberg, [email protected] Advisors Håkan Grahn, [email protected] Paul Davidsson, [email protected] A Software Engineering Master’s Thesis at the University of Karlskrona/Ronneby, 1998. Table of Contents 1 Introduction 1.1 Overview.............................................................................. 3 1.2 Current Praxis...................................................................... 4 UNIX.................................................................................
    [Show full text]
  • Mainframe History and the First User's Groups (SHARE) Dr. Steve Guendert
    Mainframe History and the First User’s Groups (SHARE) Dr. Steve Guendert “Programming” (and programming support) was an old data processing concept that originally was broadly defined as the adaptation of general-purpose devices to specific tasks. Programming therefore goes back to Herman Hollerith wiring and rewiring (programming) his equipment to handle specific jobs. By the early 1930s IBM was distributing information about novel (for the time) plugboard wiring diagrams to customers via a publication called Pointers. Some of these diagrams were created by IBMers, but more importantly, many were created by customers who were willing to share their solutions with other customers. A culture of programming support and sharing was well in place among IBM and its customers long before the S/360. Actually, it was in place long before the first IBM 701 (the Defense Calculator) computer was installed. Adapting this culture to meet the evolving requirements of its customers proved crucial to IBM’s success. In August 1952, thirty representatives from the prospective customers for the IBM 701 were invited to the IBM facility at Poughkeepsie, NY for a week long training class. This class also gave these pioneering customers their first opportunity to test some programs they had written by running them on an engineering model of the IBM 701. These customers also began sharing their programs amongst themselves. They and their installations took a great deal of professional pride in developing programs and subroutines that were effective and put in use by other installations. Several of the participants at this training class decided to continue discussing programming and mutual problems on an informal basis.
    [Show full text]
  • A Second Modernism
    A Second Modernism MIT, Architecture and the ‘Techno-Social’ Moment Edited by Arindam Dutta with Stephanie Marie Tuerk Michael Kubo Jennifer Yeesue Chuong 1 ALISE UPITIS Two or More Architectures Computers and Design at MIT until 1963 In 1962 and 1963, Christopher Alexander method of solving problems of engineering was a research affiliate at the MIT Civil design; the next two reports detail the Engineering Systems Laboratory (CESL). computer programs that primarily Alexander At the time he was completing his PhD in wrote for implementing the method.4 architecture from the Graduate School of This dual focus on developing new computer Design at Harvard University, about a year systems for engineering design while before publishing his dissertation as Notes simultaneously investigating design methods on the Synthesis of Form. At the time of its was not uncommon in the context of MIT publication, Progressive Architecture heralded engineering at the time. Discussing a research that it “could revolutionize the approach to endeavor termed the Computer -Aided Design architectural design.”1 The journal Industrial project--a joint venture of the MIT Electronic Design stated it was “one of the most Systems Laboratory, Department of Electrical important contemporary books about the Engineering, and the Design Division, art of design.”2 The Journal of the American Department of Mechanical Engineering Institute of Planners predicted that “it may initiated in 1959--Steven Coons stated: one day prove to be a landmark in design methodology.”3 Notes has
    [Show full text]
  • (OSS/FS)? Look at the Numbers!
    Why Open Source Software / Free Software (OSS/FS)? Look at the Numbers! David A. Wheeler [email protected] Why Open Source Software / Free Software (OSS/FS)? Look at the Numbers! Table of Contents Why Open Source Software / Free Software (OSS/FS)? Look at the Numbers!..........................................1 Introduction.........................................................................................................................................................2 Market Share.......................................................................................................................................................4 Reliability...........................................................................................................................................................11 Performance......................................................................................................................................................15 Scaleability.........................................................................................................................................................21 Security..............................................................................................................................................................22 Total Cost of Ownership (TCO)......................................................................................................................31 Non−Quantitative Issues..................................................................................................................................36
    [Show full text]