DOCSLIB.ORG

CERN LIBRARIES, GENEVA CERN/SPC/220 28 February, 1966

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read 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. An internal tech• nical report (DD/CO/66/I) is annexed, giving details of the future needs, the performance of the 6600, the possible ways of development and their financial implications. 2. History A major study of CERN's computing needs was made in 1963 by the European Committee and its working party, who reported that CERN should provide for a great increase in ordinary computing load over the period 1965-1969, allowing for the use of complicated on-line applications involving large programmes such as HPD and spark chamber experiments, and in addition should develop a system of remote operating consoles, whereby individual users could test and run programmes much more easily than with conventional input/output media. The report recommended the purchase of a CDC 6600 central computer, with a set of peripheral computers to pre-treat raw experi• mental data, and the addition at some time of extra storage capacity to cope with the problem of time-sharing with large programmes and many users. As a result, the CDC 6600 was purchased and installed at CERN early in 1965, and preparations for these various uses were pushed ahead, including the study of the extensions required when on-line uses became common. Programming systems and equipment were studied, and offers were requested from manufacturers for an input/ output processor and for some means of extending the central memory of the 6600 (see Annex, section 4). Meanwhile, the problem of getting the 6600 into regular use had been much worse than expected, both because of the long delays by CDC in supplying software and because of machine unreliability, which ultimately required a complete overhaul and the retuning of the cen• tral processor in November. Since then, the machine has been working 66/348/5 CERN/SPC/220 Page 2 better and a more efficient operating system has been developed, which should give a speed of-5-6 7090s with HPD in operation at the same time. As a result of these delays, there is a backlog of work, par• ticularly of film to be measured on HPD and Luciole, which will take several months to be run off, even when the new time-sharing system, SIPROS, is in full use. In broad terms, wo can say that we.have lost some six months in bringing HPD and other devices into production, and it will be a difficult job to regain this lost time. Since November, we have also been using a 32 K CDC 3400 (about equivalent to a 7090) lent to us by the firm, and we propose continuing with it until we can make other arrangements for a reserve computer as described in the last section of this paper. This experience has led us to make a complete review of the policy outlined above, including a re-estimate of the future needs of the various users. For comparison with other laboratories' programmes, wo may recall that Berkeley have just taken delivery of their 6600, and Brookhaven's is due to be installed shortly. Argonne have cancelled their arrangement for an IBM 360/92 and have ordered instead a CDC 6800 for delivery in two years' time. Berkeley will soon also have installed a CDC 6411 to increase the input/output capacity of their 6600, and have an option to buy an extended core store next year. 3. Review of Policy 3.1 Needs In 1963 the computing load at CERN was estimated to grow from the capacity of 1 IBM 7090 at the end of 1964 to between 10 and 15 7090s by the end of 1968. The detailed bases of these estimates have been reviewed very recently (see Annex, section 2), and the con• clusions are very similar, predicting a load of 8 7090s in mid 1967 and 13 7090s by mid 1968. A large fraction of this load will be provided by on-line devices, either measuring film, or collecting experimental data on the PS, and the size of many of the programmes involved will vary between 40 000 and 70 000 words. At about this time the data rates from on-line experiments could increase still further if a largo data-collecting set-up involving wire chambers or fast hodoscopes were built as part of the improvements programme. Such a project would probably have to include as an integral part a medium-sized computer for data collection and at least partial treatment of the information. For a work load of this kind, with large programmes and real time uses, it is unlikely that the 6600 as it now stands can have a capacity of more than 10 7090s, even with further develop• ments in compilers and operating systems. To reach the ultimate computing speed of the machine, and to be able to store enough pro• grammes in an accessible form to run several on-line devices and to 66/348/5 CERN/SPC/220 Page 3 begin the use of a multi-access console system, it will be necessary, as foreseen broadly in the 1963 studies, tc add some half a million words of fast-access storage to the 6600 system, and to provide an input/output processor to assemble and edit data on its way to and from the 6600. The review of needs, and also our practical experience with the 6600, raised two points - the desirability of having extra capacity in the form of a reserve computer, and the amount of time needed for system development work and testing time for now on-line equipment - which were not given sufficient weight in the 1963 studies. At that time, the need for a medium-sized computer was considered, and rejected on the grounds that it could only add a small extra capacity, and that it would not be useful in adding flexibility of operation when a time-sharing system was operating on the 6600. The poor reliability of the 6600 in the past year, and the difficulty in diagnosis and cure of faults or in installation and testing of improvements (which is intrinsic to any of the new genera• tion of very large and complicated machines), illustrate how important it is that the overall computer facility at CERN should have "fail safe" characteristics, and that therefore the 6600 should be backed up by some independent computer capacity to take care at least of urgent short-term work in case the main machine is out of action, and, possibly, to handle some parts of the production load if circumstances warrant. Further, although the need to do systems development work at CERN, for the on-line applications and a console system for example, was recognized in 1963, it was then hoped that the initial performance of the 6600 would be good enough - as it would have been if CDC had lived up to their promises on software - to provide easily spare time in 1965-1967 to do this work. Secause of the backlog of work which has built up over the past few months, and the delays in introducing a programming system adequate for our needs, this spare time will not be available. An independent reserve computer would enable development work to be continued, possibly on the second machine, possibly by off• loading the 6600 to some extent, as the 3400 has done over the past three months. Thus, to the previous requirements of adding extra storage and input/output processing to the present system, we must add the need for some independent computing capacity to act as a reserve in case the 6600 is out of action and to provide extra time for develop• ment work, or to reduce the 6600 load for certain types of work. 66/348/5 CERN/SPC/220 Page 4 3.2 Possible Solutions Various ways to satisfy these requirements individually are described in the Annex (section 4), Two possibilities for the storage and input/output development emerged from the consideration of manufacturers' replies to our request for tenders for this system, viz.
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]
  • 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]
  • The Compilation and Processing of Ibm 1401 Programs on Ibm 7090 Vol
    V' EUR 2637.e VOL. III h 'Ά EUROPEAN ATOMIC ENERGY COMMUNITY - EURATOM THE COMPILATION AND PROCESSING OF ^m. IBM 1401 PROGRAMS ON IBM 7090 VOL. Ill : THE SIMULATOR PROGRAM HÄVSh'w gbwBpwH »'¡Τ· M* m It! This doc under Commission MM of the European Atomic Energy Community (EURATOM). Neither the EURATOM Commission, epresentation, to the accuracy, completeness, or usefulness of the information con­ tained in this document, or that the use of any information, apparatus, method, or process disclosed in this document may not infringe privately owned rights; or Ü'áií·: _ Assume any liability with respect to the use of, or for damages resulting from the use of any information, disclosed in this document. k ι tø Mr κ This report is on sale at the addresses listed on cover page 4 at the price of FF 7,— FB 70,­ M 5,60 Lit. 870 Fl. 5,10 When ordering, please quote the EUR number and the title, which are indicated on the cover of each report. If MMm Printed by Guyot, s.a. Brussels, January 1966 This document was reproduced on the basis of the best available copy, .HJtUtjjj W mm/if, "Κ»:Ι;Λ ι*« mmm EUR 2637.e VOL. III THE COMPILATION AND PROCESSING OF IBM 1401 PROGRAMS ON IBM 7090 VOL. Ill : THE SIMULATOR PROGRAM by A.F.R. BROWN European Atomic Energy Community - EURATOM Joint Nuclear Research Center Ispra Establishment (Italy) Scientific Information Processing Center - CETIS Brussels. January 1966 - 60 Pages - FB 70 In the field of non-numerical data processing it is often more profitable to use a medium-size computer instead of a big one.
    [Show full text]