Systems Reference Library IBM 7090-7040 Direct Couple Operating

Total Page:16

File Type:pdf, Size:1020Kb

Systems Reference Library IBM 7090-7040 Direct Couple Operating File No. 7090-36 Form C28-6382-3 Systems Reference Library IBM 7090-7040 Direct Couple Operating System Programmer's Guide This publication contains information the programmer needs to prepare jobs for the IBM 7090-7040 Direct Couple Operating System (DCOS), i7090-PR-161. Included are discussions of basic system concepts, control cards, the Core Storage Dump Program, the Direct Couple Input/Output Executor, and a discussion of 7090 octal dump interpretation. Form C28-6382-3 Page Revised 6/11/65 By TNL N28-0157-0 PREFACE This publication describes the Direct Form C28-6392 Couple Operating System (DCOS) and the IBM 7090/7094 Programming Systems: COBOL components of it that are of primary inter­ Language, Form C28-6391 est to the applications programmer. The IBM 7090/7094 IBSYS Operating system: first section contains a general introduc­ IBJOB Processor Debugging Package, tion to DCOS that is intended to acquaint Form C28-6393 the reader with system concepts, modes of operation, and job flow. Subsequent sec­ tions include discussions of control cards, Instructions for using the IBJOB Proc­ the Core storage Dump Program, the Direct essor should be interpreted by the reader Couple Input/Output Executor, and 7090 of the above publications in light of the octal dump interpretation. DCOS configuration and oth~r charac­ teristics of DCOS. The most significant More detailed information about DCOS, considerations are the unit assignment including initial creation and system main­ specifications for the $FILE control card. tenance procedures, is contained in the These are described in Appendix A of this publication, IBM 7090-7040 Direct Couple publication. Operating System: Systems Programmer's Guide, Form C28-6383. References to the Input/Output Control System also appear in this publication. All information required by machine The Input/Output Control System is des­ operators is provided in the publication cribed in the publication IBM 7090/7094 IBM 7090-7040 Direct Couple Operating Sys­ IBSYS Operating System: Input/Output Con­ tem: Operator's Guide, Form C28-6384. trol System, Form C28-6345. Specifications for the Direct Couple The Direct Couple Operating System is feature, and descriptions of additional designed for five major machine configu­ machine instructions that facilitate its rations. use, are contained in the publication Directly Coupled processing Units--7040 to 1. 7090-DC-7040 7090/7094; 7044 to 7094/7094 II, Form 2. 7094~DC-7040 A22-6803. 3. 1094-DC-7044 4. 1094 II-DC-1044 For information on the IBJOB Processor, 5. 7094 II-DC-7040 the major subsystem of DCOS, the reader is referred to the following IBM publications: Throughout this publication, the term 7090 refers to the 1090, 7094, or 7094 II IBM 7090/7094 IBSYS Operating System: and the term 7040 refers to the 7040 or IBJCB Processor, FormC28-6389 7044. IBM 7090/7094 Programming Systems: FOR­ TRAN IV Language, Form C28-6390 The minimum machine configuration IBM 7090/7094 Programming Systems: Macro required by the distributed version of DCOS Assembly Program (HAm Language, is given in Appendix F. Major Revision (March 1965) This edition, Form C28-6382-3, is a major reV1S1on of Form C28-6382-2. This publication amplifies material pre­ viously presented, and, in some cases, provides additional material. Major changes and additions are concerned with: system messages, utility routines, and direct- and compatability-mode systems. Additions or changes are indicated by a vertical line to the left of the text; new or revised illustrations are denoted by the symbol • to the left of the caption. The following publications are made obsolete by this revision: C28-6382-2, C28-6382-1, C28-6382-0, and the Tech­ nical Newsletters N28-0145-0 and N28-0148-0. This publication was· prepared for production using an IBM computer to update the text and to control the page and line format. Page impressions for photo­ offset printing were obtained from an IBM 1403 Printer using a special print chain. Copies of this and other IBM publications can be obtained through IBM Branch Offices. A form for readers' comments appears at the back of this publication. It may be mailed directly to IBM. Address any ·additional comments concerning this publication to the IBM Corporation, Programming Systems Publications, Department 039, 1271 .Avenue of the Americas, New York, NY., 10020. o 1964 by International Businp.ss Machines Corporation CONTENTS INTRODUCTION 7 Transfer To D~mp Instructions • 24 DIRECT COUPLE OPERATING SYSTEM CONCEPTS 8 Dump Parameters • 24 IBM 7090 Data Processing System 8 IBM 7040 Data Processing System 8 Machine Status at the End of a Dump 25 IBM 1402 Card Read Punch · 8 IBM 1403 Printer . · · · 8 DIRECT COUPLE INPUT/OUTPUT EXECUTOR 27 IBM 1014 Remote Inquiry Unit · · · · 8 IBH 729 Magnetic Tape units 8 DC-IOEX Communication Region Table 27 IBM 1301 Disk Storage · · · · 8 IBM 7320 Drum Storage · · · · 9 unit Control Block 29 · · · · Word 1 • • • • • 29 Job Processing • • • • • • 9 ~ord 2 • • • • • • • 30 DCOS Multiprocessor •••• 9 Word 3 • 30 IBM 7090 Operating System with DC Word 4 q • • • • 30 Capability ••••••••• 10 Maintenance of Unit Control Block 7040/7044 IBJOB Tape Blocking Fields '. • • • • • • • • 30 Utility Routines 11 Using The DC-IOEX Trap Supervisor • 30 Operating Modes • • • 11 Determining the Availability of a Direct Mode 11 Unit • • • • • • • • • 30 Compatibility Mode. 11 Call to DC-IOEX 30 Job Flow 12 Select Routines • 31 Input Stage 12 Select Routine Exits 31 Setup Stage 12 Location MODSW • • • • • 31 Execution Stage 12 Design of Select Routines, Select Breakdown Stage 13 Plus Entry • • • • • • • • • • 31 Punch Stage 13 Design of Select Routines, Select Print Stage •••• 13 Minus Entry • • • • • • • • • • • • 32 Purge Stage 13 Sense Indicators • • • • • • • • • • 32 Suppression of the IOEX Redundancy Example of Typical Job Flow 13 Message • • • • • •• • • • • • 32 Functional 7090 System Unit (IOBASE) Location • COMM • • • • • • • • • 32 Configurations • • • • • • • • 14 General Considerations in the Design of Select Routines 33 CONTROL CARDS • • • • • 15 General Control Card Format 15 Nondata Selects 33 $JOB Card •••• 15 $EXECUTE Card 15 DC-IOEX Utility Routines 34 $ROW Card 16 Message Writer • 34 $ENDROW Card • • • • • • 16 Message Length • • • • • 35 $IOBASE Card • • • 17 Alphameric Punch • .• • • 35 $SETUP Card • • • • 17 Post-Mortem Dump • • • • 35 $SETUP Card Option Specifications 18 Binary-to-Decimal Conversion--AC $ASSIGN Card 19 Decrement • • • • • • • • • • • 35 $ATEND Card • • • • 20 Binary-to-Decimal Conversion--AC $DATA, $EOF, iEOF, and i Cards • 20 Address • • • • • • • • • • • • • • 35 $ID Card • • • • • • • • 20 Binary-to-BCD Octal Conversion--MQ $* Card 21 Decrement • • • • • • • • • • 35 $PAUSE Card 21 Binary-to-BCD Octal Utility Routines Specified on Conversion--S,1-14 of MQ 35 $UTILITY Cards •••• 21 Pause Routines • • • • 35 Examples of Deck Setups 22 Symbolic Unit Conversion •• 36 Convert and Add Unit Designation to SYSTEM CORE STORAGE DUMP PROGRAM 24 Message • • • • • • • • • • • • 36 GENERAL PROGRAMMING CONSIDERATIONS 37 Direct- and Compatibility-Mode Systems 37 Direct-Mode Systems • • • • 38 Compatibility-Mode Systems 38 GUIDE TO 7090 OCTAL DUMP INTERPRETATION 40 Non-DC-IBSYS Jobs ••• • • • 40 Data Channel-Trap Simulation • • 40 DC-IBSYS Locations • • • • • • • 41 communication region locations • 42 Examining Unit Control Blocks 44 APPENDIX A: IBJOB UNIT ASSIGNMENT-DCOS 46 Unit Assignment Options 46 General Unit Assignment Considerations •••• 47 APPENDIX B: MESSAGES... 48 APPENDIX C: CONTROL CARD FORMAT INDEX. 58 DC-IBSYS/DCMUP Control Cards 58 System Editor Control Cards • • 59 7040/7044 IBJOB Tape Blocking Utility Control Cards ••• • • • • •• 60 APPENDIX D: CONTROL CARD CHECK LIST 61 pC-IBSYS/DCMUP Control Cards 61 System Editor Control Cards • • 62 APPENDIX E. SPECIAL CONSIDERATIONS; COMPATIBILITY MODE OPERATION • 64 FORTRAN II Monitor System 64 709C/7094 Sort • • • • • • • 64 APPENDIX F: MACHINE CONFIGURATION • •• 66 ILLUSTRATIONS Figure 1. Direct Couple Operating Sys- tem--General Machine Configuration 8 Figure 2. Phases of Processing . • •• 9 Figure 3. DC-IBSYS Monitor Organization. • • • • • • • • . • .• 10 Figure 4. IBM 7090 Operating System with DC Capability (DC-IBSYS) 11 Figure 5. Stages of Processing for Non- Utility Jobs. • • • • • • • 12 Figure 6. Direct-Mode System Unit FUnctions (IOBASE 0) • • . • • 14 Figure 7. IOBASE 1 • • • • • • . • •• 14 Figure 8. IOBASE 2 • • • • • • 14 Figure 9. Sample $ROW-$ENDROW Application • • • • • • • 16 Figure 10. Sample Deck Setup--FORTRAN Compilation and IBMAP Assembly • • 22 Figure 11. Sample Deck Setup--One- Segment FORTRAN Compilation and Execution • • • • . • • • • • • 23 Figure 12. Sample Deck Setup--Two- Segment Job • • • • • • • • • 23 Figure 13. Sample Deck Setup--Object Program on Cards • • • • • • . • • •. 23 Figure 14. Sample Deck Setup--System on Tape • • • • • • • • • • • • • • • 23 Figure 15. Core Storage Dump Formats 26 Figure 16. DC-IOEX Communication Table • • • • • • • • • • • 28 Figure 17. Unit Control Block. 30 Figure 18. DC-IBSYS Locations. 42 Figure 19. Communication Region Locations •••••• • • • 43 Figure 20. Contents of Sample Unit Control Block . • • • . 45 INTRODUCTION The Direct Couple Operating System All 7090 input/output requirements are (DCOS) is a set of supervisory routines handled by 7040 routines. The 7607 Data that coordinate job processing on systems Channel and its associated input/output having the Direct Couple feature. DCOS devices are simulated by
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]
  • CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966
    CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966 CM-P00095068 ORGANISATION EUROPÉENNE POUR LA RECHERCHE NUCLÉAIRE CERN EUROPEAN ORGANIZATION FOR NUCLEAR RESEARCH SCIENTIFIC POLICY COMMITTEE Thirty-eighth Meeting 8 March, 1966 EXTENSIONS TO THE CERN COMPUTING FACILITIES by Dr. M.G.N. Hine The attached paper contains a review of CERN's needs from its central computing facilities, both in the near future and as far as 1969-1970. It describes possible ways in which these needs might be met within the budget forecasts, and suggests an optimum way to proceed. The scientific policy is to be discussed at the Scientific Policy Committee meeting on 8th March. If the policy line is cleared at that meeting, the Finance Committee could start discussion of the contractual implications at its meeting on 10th March. The Finance Committee would not be pressed to give final decisions at that meeting about contract adjudications, but those decisions will be needed in the near future. 66/348/5 CERN/SPC/220 EXTENSIONS TO THE CERN COMPUTING FACILITIES 1. Introduction The need to continue the development of computing facilities at CERN in order to keep pace with the rapidly growing use of com• puting and digital techniques in high-energy physics has been ex• plained on several occasions to the Scientific Policy Committee and the Finance Committee, and money has been reserved in the future budget forecasts for this purpose. A review of our needs has been made recently in the light of a year's experience of use of the CDC 6600 and associated equipment, and this paper describes the conclusions and the policy we propose to follow.
    [Show full text]
  • An Experimental Time-Sharing System
    335 AN EXPERIMENTAL TIME-SHARING SYSTEM Fernando J. Corbato, Marjorie Merwin-Daggett, Robert C. Daley Computer Center, Massachusetts Institute of Technology Cambridge, Massachusetts summary It is the purpose of this paper to discuss The motivation for time-shared computer briefly the need for time-sharing, some of the usage arises out of the slow man-computer inter- implementation problems, an experimental time- action rate presently possible with the bigger, sharing system which has been developed for the more advanced computers. This rate has changed contemporary IBM 7090, and finally a scheduling little (and has become worse in some cases) in algorithm of one of us (FJC) that illustrates the last decade of widespread computer use. lO some of the techniques which may be employed to enhance and be analyzed for the performance In part, this effect has been due to the limits of such a time-sharing system. fact that as elementary problems become mast- ered on the computer, more complex problems immediately become of interest. As a result, Introduction larger and more complicated programs are written to take advantage of larger and faster computers. The last dozen years of computer usage have This process inevitably leads to more programm- seen great strides. In the early 1950's, the ing errors and a longer period of time required problems solved were largely in the construction for debugging. Using current batch monitor and maintenance of hardware; in the mid-1950's, techniques, as is done on most large computers, the usage languages were greatly improved with each program bug usually requires several hours the advent of compilers; now in the early 1960's, to eliminate, if not a complete day.
    [Show full text]
  • Systems Reference Library IBM 7090-7040 Direct
    File No. 7090-36 Form C28-6383-2 Systems Reference Library IBM 7090-7040 Direct Couple Operating System Systems Programmer's Guide This publication contains information useful to programmers who require a thorough understanding of the IBM 7090-7040 Direct Couple Operating System (DCOS), #7090-PR-161. This system consists of the following parts: 7090/7094 Operating System (IBSYS) 7040/7044 Control Program (DCMUP) The publication provides descriptions of general DCOS program logic, the format of the DCOS System Library, the Operating System Monitor (DC-IBSYS), and the lnput/Output Executor (DC-IOEX). It also includes instructions for system library preparation and maintenance. Separate publications contain descriptions of the compo­ nents of the 7090/7094 Operating System (IBSYS). Other related publications contain information needed by applica­ tions programmers and instructions for machine operators. Form C28-6383-2 Page Revised 6/11/65 By TNL N28-0158-0 PREFACE This publication is primarily intended IBM 7040/7044 Principles of Operation, for systems programmers who are responsible Form A22-6649 for the maintenance of the 7090-7040 Direct Couple Operating System (DCOS} and any modifications to it at the installation. IBM 7090 Principles of Operation, Form It may also be of interest to individuals A22-6528 who desire a more thorough understanding of the system. IBM 7094 principles of Operation, Form A22-6703 The reader of this publication is Directly Coupled Processing Units--7040 assumed to be familiar with the contents of to 7090/7094; 7040 to 7094/7094 II, Form the publication IBM 7090-7040 Direct Couple A22-6803 Operating System: Programmer's Guide, Form C28-6382.
    [Show full text]
  • Computing at CERN Units
    Inside the computer room where the CDC 6600 has served as CERN's main computer. To the left and in the background are magnetic tape Computing at CERN units. In the foreground is the console where the operators are in communication with the A review of the past, present and future of computer's operating system. On the displays computing at CERN concentrating on the large they can see which programs are running central computers which bear the brunt at that time and also the various stage which of CERN's workload. the programs going through the computer have reached. D. Ball spared a painful running-in period. The Past The growth in demand for com­ The FORTRAN era came with it. The puting at CERN continued unabated, Computing at CERN started in the problem of the mismatch of me­ amounting to a doubling each year, Autumn of 1958 with the installation of chanical input/output speed to that and this situation, plus the increasing a Ferranti Mercury, which was, for its of electronic computation soon be­ importance of computers in the work time, a modern and powerful Euro­ came apparent and a small ' satellite ' of the Laboratory, necessitated a jump pean-built computer. It was bought to computer, an IBM 1401, was installed in computing capacity preferably of provide data-handling facilities for to relieve the 709 of some of the the order of a factor of ten. The only CERN's physics programme. Its in­ drudgery. In 1962 a flying spot digit­ computer which could give this in­ stallation taught CERN that computers izer to measure bubble chamber film crease was the Control Data Corpo­ are a mixed blessing, requiring a staff was connected to the IBM 709 — the ration 6600 and, in March 1964, CERN of experts to nurse them along parti­ first use of computers on-line at placed its order.
    [Show full text]
  • F.T. Mcclure Computing Center Development
    ROBERT P. RICH F. T. McCLURE COMPUTING CENTER DEVELOPMENT The development of APL's F. T. McClure Comput­ Acquisition of the IBM 7090/1401 combination in ing Center has been guided by two complementary 1959 (Fig. 3) provided the Fortran language to the needs: computing power (capacity) and specific capa­ APL computing community, with access to programs bilities. written by a much larger community of Fortran users. Computing power is a measure of how much com­ Although still restricted to batch, several jobs could puting can be done per unit time, regardless of what be submitted to the system at one time, in both assem­ is being computed or the mode of man-machine in­ bly language and in Fortran. The existence of sepa­ teraction. It is measured in operations per second and rate channels made it possible for computation to has grown, since 1966, at an average annual compound proceed in parallel with input/output operations. Be­ rate of about 180/0. The growth has been impelled by ginnings were made in information retrieval and text processing during that period, and the Laboratory's 1. Growth in the staff during the early years; financial work was shifted to a separate IBM 1401. 2. The change in work habits of the staff to take The system grew to an IBM 7094 in 1962 and then advantage of increasing computer capabilities; to two 7094s in 1963. The 1401 was replaced by an IBM 3. The shift in APL programs made possible by 7040 and an IBM 1410 in response to the mentioned those capabilities (Transit, Submarine Tech­ growth in required computing power.
    [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]
  • IBM 7090/7094 Simulator Usage 01-Dec-2008
    IBM 7090/7094 Simulator Usage 01-Dec-2008 COPYRIGHT NOTICE The following copyright notice applies to the SIMH source, binary, and documentation: Original code published in 1993-2008, written by Robert M Supnik Copyright (c) 1993-2008, Robert M Supnik Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL ROBERT M SUPNIK BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. Except as contained in this notice, the name of Robert M Supnik shall not be used in advertising or otherwise to promote the sale, use or other dealings in this Software without prior written authorization from Robert M Supnik. 1 Simulator Files.............................................................................................................3
    [Show full text]
  • Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary
    Compatible Time-Sharing System (1961-1973) Fiftieth Anniversary Commemorative Overview The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview The design of the cover, half-title page (reverse side of this page), and main title page mimics the design of the 1963 book The Compatible Time-Sharing System: A Programmer’s Guide from the MIT Press. The Compatible Time Sharing System (1961–1973) Fiftieth Anniversary Commemorative Overview Edited by David Walden and Tom Van Vleck With contributions by Fernando Corbató Marjorie Daggett Robert Daley Peter Denning David Alan Grier Richard Mills Roger Roach Allan Scherr Copyright © 2011 David Walden and Tom Van Vleck All rights reserved. Single copies may be printed for personal use. Write to us at [email protected] for a PDF suitable for two-sided printing of multiple copies for non-profit academic or scholarly use. IEEE Computer Society 2001 L Street N.W., Suite 700 Washington, DC 20036-4928 USA First print edition June 2011 (web revision 03) The web edition at http://www.computer.org/portal/web/volunteercenter/history is being updated from the print edition to correct mistakes and add new information. The change history is on page 50. To Fernando Corbató and his MIT collaborators in creating CTSS Contents Preface . ix Acknowledgments . ix MIT nomenclature and abbreviations . x 1 Early history of CTSS . 1 2 The IBM 7094 and CTSS at MIT . 5 3 Uses . 17 4 Memories and views of CTSS . 21 Fernando Corbató . 21 Marjorie Daggett . 22 Robert Daley . 24 Richard Mills . 26 Tom Van Vleck . 31 Roger Roach .
    [Show full text]
  • History and Evolution of IBM Mainframes Over the 60 Years Of
    History and Evolution of IBM Mainframes over SHARE’s 60 Years Jim Elliott – z Systems Consultant, zChampion, Linux Ambassador IBM Systems, IBM Canada ltd. 1 2015-08-12 © 2015 IBM Corporation Reports of the death of the mainframe were premature . “I predict that the last mainframe will be unplugged on March 15, 1996.” – Stewart Alsop, March 1991 . “It’s clear that corporate customers still like to have centrally controlled, very predictable, reliable computing systems – exactly the kind of systems that IBM specializes in.” – Stewart Alsop, February 2002 Source: IBM Annual Report 2001 2 2015-08-12 History and Evolution of IBM Mainframes over SHARE's 60 Years © 2015 IBM Corporation In the Beginning The First Two Generations © 2015 IBM Corporation Well, maybe a little before … . The Computing-Tabulating-Recording Company in 1911 – Tabulating Machine Company – International Time Recording Company – Computing Scale Company of America – Bundy Manufacturing Company . Tom Watson, Sr. joined in 1915 . International Business Machines – 1917 – International Business Machines Co. Limited in Toronto, Canada – 1924 – International Business Machines Corporation in NY, NY Source: IBM Archives 5 2015-08-12 History and Evolution of IBM Mainframes over SHARE's 60 Years © 2015 IBM Corporation The family tree – 1952 to 1964 . Plotting the family tree of IBM’s “mainframe” computers might not be as complicated or vast a task as charting the multi-century evolution of families but it nevertheless requires far more than a simple linear diagram . Back around 1964, in what were still the formative years of computers, an IBM artist attempted to draw such a chart, beginning with the IBM 701 of 1952 and its follow-ons, for just a 12-year period .
    [Show full text]
  • C:\Users\Owner\Desktop\Stories\The IBM 1401.Wpd
    The IBM 1401 I joined IBM in the late summer of 1959, Most, if not all of the preceding computers and that fall, took a 1-week class on the had memory units of words, all of the same programming of the 1401. I then taught size. Decimal based computer words several courses to customers for the usually were 10 or so digits long with a following 6 months. I also programmd it sign. The binary machines had words of 32 for 6 more years and found it to be an or, in the case of the IBM 7090, 36 bits. intriguing machine. So typically, they could handle integers as large as +/-9,999,999,999 or 2 31 , which was The first noticeable thing was the 1403 +/-36,364,056,439. Arithmetic in prior printer which printed at 600 lines per computers was carried out in special minute. Five sets of printable characters registers on these words. If one wanted were contained on a chain that rotated at more digits in a calculation, one would high speed past a set of 132 hammers. have to do operations on multiple words, When the appropriate character passed the and handle the overflows or carries from place where it was to be printed, the the lower order to the higher order word. hammer behind that position would fire, making the imprint. It was quite noisy, in But the 1401’s memory was made up of spite of the acoustically insulated box 8-bit bytes, as current computers are – but around it, and someone programmed a print with a twist.
    [Show full text]
  • Operating System Roots
    Operating System Roots By Robert L. Patrick Written: December, 2006 CHM Reference number: R0369.2017 Operating System Roots By Robert L. Patrick Author Sketch: U of Nevada, engineering USAF 1951-1959: Convair, GM Research, CEIR, CSC 1959-1992: Independent consultant 1992: Retired Abstract: Robert L. Patrick describes the various computer systems he worked on in the early years of computing. His review covers the IBM Card Programmed Calculator through the IBM 701 with the Speedcode interpretive programming system through the IBM 704 with an early FORTRAN compiler. This was followed by the IBM 709 with the SOS operating system, developed jointly SHARE and IBM, and then the IBM 7090 with the IBSYS operating system developed by IBM. Successful features from all of these operating systems were incorporated into the design of System/360 when it was released in the mid-1960s. Introduction To understand operating system software, it helps to go back to the beginning. In the late 1940s, some engineers at Northrop Aviation (now Northrop-Grumman Corp.) cable-connected an IBM tabulator to an IBM calculating punch and the Card Programmed Calculator was born. IBM delivered CPCs in kit form consisting of manuals, big boxes of hardware, blank plugboards, and about 50 pounds of wires of various lengths. In 1949, IBM sponsored a seminar to discuss using the CPC as a general purpose, externally programmed, engineering computer. About this same time a team under Ev Yowell (at the National Bureau of Standards center on the UCLA campus) devised a set of three-address, decimal plugboards to support engineering calculations on the CPC.
    [Show full text]