History and Evolution of IBM Mainframes
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
The Operating System Handbook Or, Fake Your Way Through Minis and Mainframes
The Operating System Handbook or, Fake Your Way Through Minis and Mainframes by Bob DuCharme MVS Table of Contents Chapter 22 MVS: An Introduction.................................................................................... 22.1 Batch Jobs..................................................................................................................1 22.2 Interacting with MVS................................................................................................3 22.2.1 TSO.........................................................................................................................3 22.2.2 ISPF........................................................................................................................3 22.2.3 CICS........................................................................................................................4 22.2.4 Other MVS Components.........................................................................................4 22.3 History........................................................................................................................5 Chapter 23 Getting Started with MVS............................................................................... 23.1 Starting Up.................................................................................................................6 23.1.1 VTAM.....................................................................................................................6 23.1.2 Logging On.............................................................................................................6 -
IBM System Z Functional Matrix
IBM System z July 2013 IBM System z Functional Matrix IBM System z This functional matrix consists of a list of features and functions that are supported on IBM System z® servers (this includes the IBM zEnterprise ® EC12 (zEC12), IBM zEnterprise BC12 (zBC12), IBM zEnterprise 196 (z196), IBM zEnterprise 114 (z114), IBM System z10 ® Enterprise Class (z10 ™ EC), IBM System z10 Business Class ™ (z10 BC), IBM System z9 ® Enterprise Class (z9 ® EC), and IBM System z9 Business Class (z9 BC). It is divided into nine functional areas; – Application Programming Interfaces, – Cryptographic features, – I/O, – Business On Demand, – Parallel Sysplex ®, – Performance, – Processor Resource Systems Manager (PR/SM ™) – Reliability, Availability, Serviceability (RAS) – IBM zEnterprise BladeCenter ® Extension (zBX) There is also a legend at the end of the matrix to identify the symbols that are being used. Note: This matrix is not intended to include services, RPQs or specific quantities or measurements related performance, memory size, bandwidth, etc. The intention of this matrix is to provide a comparison of the standard and optional features for the various System z servers. For further details on the features and functions listed in the tables, refer to the system specific reference guide documentation. This document is available from the Library area of Resource Link ™ at: www.ibm.com/servers/resourcelink Key: S = standard O = optional - = not supported zEnterprise System z10 System z9 ™ Application Programming Interface (API) ™ zEC12 zBC12 z196 z114 -
Big Blue in the Bottomless Pit: the Early Years of IBM Chile
Big Blue in the Bottomless Pit: The Early Years of IBM Chile Eden Medina Indiana University In examining the history of IBM in Chile, this article asks how IBM came to dominate Chile’s computer market and, to address this question, emphasizes the importance of studying both IBM corporate strategy and Chilean national history. The article also examines how IBM reproduced its corporate culture in Latin America and used it to accommodate the region’s political and economic changes. Thomas J. Watson Jr. was skeptical when he The history of IBM has been documented first heard his father’s plan to create an from a number of perspectives. Former em- international subsidiary. ‘‘We had endless ployees, management experts, journalists, and opportunityandlittleriskintheUS,’’he historians of business, technology, and com- wrote, ‘‘while it was hard to imagine us getting puting have all made important contributions anywhere abroad. Latin America, for example to our understanding of IBM’s past.3 Some seemed like a bottomless pit.’’1 However, the works have explored company operations senior Watson had a different sense of the outside the US in detail.4 However, most of potential for profit within the world market these studies do not address company activi- and believed that one day IBM’s sales abroad ties in regions of the developing world, such as would surpass its growing domestic business. Latin America.5 Chile, a slender South Amer- In 1949, he created the IBM World Trade ican country bordered by the Pacific Ocean on Corporation to coordinate the company’s one side and the Andean cordillera on the activities outside the US and appointed his other, offers a rich site for studying IBM younger son, Arthur K. -
The Advent of Recursion in Programming, 1950S-1960S
The Advent of Recursion in Programming, 1950s-1960s Edgar G. Daylight?? Institute of Logic, Language, and Computation, University of Amsterdam, The Netherlands [email protected] Abstract. The term `recursive' has had different meanings during the past two centuries among various communities of scholars. Its historical epistemology has already been described by Soare (1996) with respect to the mathematicians, logicians, and recursive-function theorists. The computer practitioners, on the other hand, are discussed in this paper by focusing on the definition and implementation of the ALGOL60 program- ming language. Recursion entered ALGOL60 in two novel ways: (i) syn- tactically with what we now call BNF notation, and (ii) dynamically by means of the recursive procedure. As is shown, both (i) and (ii) were in- troduced by linguistically-inclined programmers who were not versed in logic and who, rather unconventionally, abstracted away from the down- to-earth practicalities of their computing machines. By the end of the 1960s, some computer practitioners had become aware of the theoreti- cal insignificance of the recursive procedure in terms of computability, though without relying on recursive-function theory. The presented re- sults help us to better understand the technological ancestry of modern- day computer science, in the hope that contemporary researchers can more easily build upon its past. Keywords: recursion, recursive procedure, computability, syntax, BNF, ALGOL, logic, recursive-function theory 1 Introduction In his paper, Computability and Recursion [41], Soare explained the origin of computability, the origin of recursion, and how both concepts were brought to- gether in the 1930s by G¨odel, Church, Kleene, Turing, and others. -
Computers and Automation
. 7 .7 BP S' J I i2z7itltJ2f computers and automation COMPUTERS AND WAR SAFETY CONTROL A PICTORIAL REPORT ON COMPUTER APPLICATIONS JANUARY 1962 / • Vol. 11 - No.1 GET RESULTS AND RELAXATION .. DIVIDENDS FROM STATISTICAL'S DATA-PROCESSING • oj ~/ si ---0--- rr e~ /~ When data-processing problems s( put the pressure on you, you'll find n the "safety valve" you need at q STATISTICAL. A wealth of experience is always ready to go to work for you "0: here. Behind every assignment is a searching understanding of management problems and solutions ... gained in serving America's top companies since 1933. From this experience comes the consistently-high quality service you would expect from America's oldest and largest independent data-processing and computer service. Sophisticated methods. Responsible personnel. The latest electronic equipment. Coast-to-coast facilities. Advantages like these add up to "know-how" and TABULATING CORPORATION C "show-how" that can not be acquired overnight. il NATIONAL HEADQUARTERS n This experience-in-depth service is available to 104 South Michigan Avenue-Chicago 3, Illinois a you day or night. A call to our m~arest OFFICES IN PRINCIPAL CITIES - COAST TO COAST data-processing and computer center will bring you the results you want ... and relaxation. ,,1/ -/p~ THE STATISTICAL MARK OF EXCELLENCE I 2 CO~IPUTERS and AUTOMATION for January, 1962 c ester, leI. / Park, ~. Y. Hyde U. S. 'J". Y. geles, City, ment. Lynn- Lab., :trical Alto, \rich. bury, Mass. '" Co., ~ssing Iberg, Ither, Icker- Ger- IS. Abbe 1 Mi- I des -- / "mus, Tele- data Alto, \Iich. -
IBM Global Services: a Brief History
IBM Global Services: A Brief History IBM Corporate Archives May 2002 2405SH01 2 OVERVIEW Background In 1991 IBM was a $64.8 billion company, of which less than $6 billion was derived from non-maintenance services. Ten short years later, the business of information technology (IT) services alone generated more than 40 percent of IBM’s $86 billion in sales and had become the single largest source of revenue in IBM’s portfolio. How did that happen? It was partly the result of old-fashioned hard work and serious commitment: growing customer by customer; building disciplined management and financial systems; and investing to hire and train experts in everything from IT consulting to systems architecture and Web services. IBM used its financial strength to fund the expensive push into outsourcing, and the company placed informed bets on the future in areas such as IT utility services (“e-business on demand”) and hosted storage. But most important, the success of IBM Global Services came from something very simple: a clear understanding of customers’ needs. IBM saw that technology and business were converging to create something new and challenging for every kind of enterprise. And IBM had the deep experience in both areas to help its customers bring them together most effectively. The following pages offer a brief look at the history and growth of the organization that is today IBM’s top revenue generator. Definitions What are “services?” In the IT world, that broad term has encompassed dozens of offerings and meanings, including consulting, custom programming, systems integration (designing, building and installing complex information systems), systems operations (in which a vendor runs part or all of a company’s information systems), business innovation services (such as supply chain management), strategic outsourcing, application management services, integrated technology services (such as business recovery), networking services, learning services, security services, storage services and wireless services. -
IBM System Z9 Enterprise Class
The server built to help optimize your resources throughout the enterprise IBM System z9 Enterprise Class A “classic” might just be the best Today’s market finds that business needs are changing, and having a com petitive advantage isn’t always about having more or being bigger, but more about being smarter and responding faster to change and to your clients. Often, being reactive to change has led to infrastructures with mixed technolo gies, spread across an enterprise, that are complex and difficult to control and costly to manage. Integration of appli cations and data is limited and difficult. Using internal information to make insightful decisions for the company Highlights can be difficult because knowing you are using the “best” data—that which is ■ Strengthening the role of the ■ Continued improvement in most current and complete—may not mainframe as the data hub of IBM FICON® performance and be possible. the enterprise throughput In many situations, investments have ■ New versatile capacity settings ■ On demand innovative tech been made in disparate technologies designed to optimize capacity nologies to help meet ever- that may fall short of meeting their and cost changing business demands goals. Merging information from one branch to another may not be possible ■ IBM System z9™ Integrated and so company direction is set with Information Processor (IBM zIIP) is designed to improve resource optimization and lower the cost of eligible work only a portion of the data at hand, and help achieve advanced I/O function and But data management can be a big in a global economy that can really hurt. -
Ist Das Z/OS (Objekt-) Relationale Datenbank-Produkt
Betriebssysteme it-Akademie Bayern z/OS und OS/390 Lehrgang 2009 Prof. Dr.-Ing. Wilhelm G. Spruth Teil 9b z/OS Subsysteme bs 0901 ww6 © copyright W. G. Spruth, 10-2000 wgs 03-95 Server Zugriff Unterschied zwischen Einzelplatzrechner und Client/Server Betriebssystemen. NT und Unix werden für beides eingesetzt. OS/390 ist ein reinrassiges Server Betriebssystem. Andere Beispiele für Server Betriebssysteme: Tandem Pathway, DEC Vax. Ein Server Zugriff benötigt spezielle Client Software. Möglichkeiten für selbstgeschriebene Klient-Anwendungen: Sockets, RPC, Corba, DCOM, RMI Zeilenorientierte Klienten: Unix Server Telnet Client OS/390 Server 3270 Client Vax Server VT 100 Client Klienten mit graphischer Oberfläche: NT Server Citrix Client WWW Server Browser Client SAP R/3 Server SAPGUI Client OS/390 Server Servlet, Java Server Page Client Client Server NT OS/390 LAN oder Internet Jedi 3270 Client Telnet, TN3270 es 0537 ww6 wgs 07-00 Typical online use Typical online use 1. A customer uses an ATM, which presents a user- friendly interface for various functions: Withdrawal, query account balance, deposit, transfer, or cash advance from a credit card account. 2. Elsewhere in the same private network, a bank employee in a branch office performs operations such as consulting, fund applications, and money ordering. 3. At the bank’s central office, business analysts tune transactions for improved performance. Other staff use specialized online systems for office automation to perform customer relationship management, budget planning, and stock control. 4. All requests directed to the mainframe computer for processing. 5. Programs running on the mainframe computer perform updates and inquires to the database management system (for example, DB2). -
Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected]
IBM-ACS: Reminiscences and Lessons Learned From a 1960’s Supercomputer Project * Lynn Conway Professor of Electrical Engineering and Computer Science, Emerita University of Michigan, Ann Arbor, MI 48109-2110 [email protected] Abstract. This paper contains reminiscences of my work as a young engineer at IBM- Advanced Computing Systems. I met my colleague Brian Randell during a particularly exciting time there – a time that shaped our later careers in very interesting ways. This paper reflects on those long-ago experiences and the many lessons learned back then. I’m hoping that other ACS veterans will share their memories with us too, and that together we can build ever-clearer images of those heady days. Keywords: IBM, Advanced Computing Systems, supercomputer, computer architecture, system design, project dynamics, design process design, multi-level simulation, superscalar, instruction level parallelism, multiple out-of-order dynamic instruction scheduling, Xerox Palo Alto Research Center, VLSI design. 1 Introduction I was hired by IBM Research right out of graduate school, and soon joined what would become the IBM Advanced Computing Systems project just as it was forming in 1965. In these reflections, I’d like to share glimpses of that amazing project from my perspective as a young impressionable engineer at the time. It was a golden era in computer research, a time when fundamental breakthroughs were being made across a wide front. The well-distilled and highly codified results of that and subsequent work, as contained in today’s modern textbooks, give no clue as to how they came to be. Lost in those texts is all the excitement, the challenge, the confusion, the camaraderie, the chaos and the fun – the feeling of what it was really like to be there – at that frontier, at that time. -
Key Themes in Histories of IBM
James W. Cortada Change and Continuity at IBM: Key Themes in Histories of IBM IBM has been the subject of considerable study by historians, economists, business management professors, and journalists. This essay surveys the various writings on the company, placing their contributions in a roughly chronological account of the company’s history, from its early days in tabulating through to its dominance of global markets in computing. The essay includes well-known studies of IBM in addition to more obscure accounts. It emphasizes the need to consider the com- pany’s culture along with its technological and managerial changes in order to grasp the reasons for its longevity. Keywords: IBM, Thomas J. Watson Sr., Thomas J. Watson Jr., Arthur K. (Dick) Watson, Herman Hollerith, IBM World Trade Corporation his essay provides a guide to the voluminous writings on IBM by Thistorians and by others whose work is useful to historians, including IBM employees and management and technology experts. This is a global history and looks at sources in English and in other lan- guages. To do so, it also traces briefly the continuities and discontinuities in IBM’s strategy and culture over time, and highlights key events in its history.1 1 For general works on IBM, see Robert Sobel, I.B.M., Colossus in Transition (New York, 1981); Saul Engelbourg, International Business Machines: A Business History (New York, 1976); James W. Cortada, Before the Computer: IBM, NCR, Burroughs, and Remington Rand and the Industry They Created, 1865–1956 (Princeton, N.J., 1993); Emerson W. Pugh, Building IBM: Shaping an Industry and Its Technology (Cambridge, Mass., 1995). -
IBM Z Server Time Protocol Guide
Front cover Draft Document for Review August 3, 2020 1:37 pm SG24-8480-00 IBM Z Server Time Protocol Guide Octavian Lascu Franco Pinto Gatto Gobehi Hans-Peter Eckam Jeremy Koch Martin Söllig Sebastian Zimmermann Steve Guendert Redbooks Draft Document for Review August 3, 2020 7:26 pm 8480edno.fm IBM Redbooks IBM Z Server Time Protocol Guide August 2020 SG24-8480-00 8480edno.fm Draft Document for Review August 3, 2020 7:26 pm Note: Before using this information and the product it supports, read the information in “Notices” on page vii. First Edition (August 2020) This edition applies to IBM Server Time Protocol for IBM Z and covers IBM z15, IBM z14, and IBM z13 server generations. This document was created or updated on August 3, 2020. © Copyright International Business Machines Corporation 2020. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Draft Document for Review August 3, 2020 8:32 pm 8480TOC.fm Contents Notices . vii Trademarks . viii Preface . ix Authors. ix Comments welcome. .x Stay connected to IBM Redbooks . xi Chapter 1. Introduction to Server Time Protocol . 1 1.1 Introduction to time synchronization . 2 1.1.1 Insertion of leap seconds . 2 1.1.2 Time-of-Day (TOD) Clock . 3 1.1.3 Industry requirements . 4 1.1.4 Time synchronization in a Parallel Sysplex. 6 1.2 Overview of Server Time Protocol (STP) . 7 1.3 STP concepts and terminology . 9 1.3.1 STP facility . 9 1.3.2 TOD clock synchronization . -
MTS on Wikipedia Snapshot Taken 9 January 2011
MTS on Wikipedia Snapshot taken 9 January 2011 PDF generated using the open source mwlib toolkit. See http://code.pediapress.com/ for more information. PDF generated at: Sun, 09 Jan 2011 13:08:01 UTC Contents Articles Michigan Terminal System 1 MTS system architecture 17 IBM System/360 Model 67 40 MAD programming language 46 UBC PLUS 55 Micro DBMS 57 Bruce Arden 58 Bernard Galler 59 TSS/360 60 References Article Sources and Contributors 64 Image Sources, Licenses and Contributors 65 Article Licenses License 66 Michigan Terminal System 1 Michigan Terminal System The MTS welcome screen as seen through a 3270 terminal emulator. Company / developer University of Michigan and 7 other universities in the U.S., Canada, and the UK Programmed in various languages, mostly 360/370 Assembler Working state Historic Initial release 1967 Latest stable release 6.0 / 1988 (final) Available language(s) English Available programming Assembler, FORTRAN, PL/I, PLUS, ALGOL W, Pascal, C, LISP, SNOBOL4, COBOL, PL360, languages(s) MAD/I, GOM (Good Old Mad), APL, and many more Supported platforms IBM S/360-67, IBM S/370 and successors History of IBM mainframe operating systems On early mainframe computers: • GM OS & GM-NAA I/O 1955 • BESYS 1957 • UMES 1958 • SOS 1959 • IBSYS 1960 • CTSS 1961 On S/360 and successors: • BOS/360 1965 • TOS/360 1965 • TSS/360 1967 • MTS 1967 • ORVYL 1967 • MUSIC 1972 • MUSIC/SP 1985 • DOS/360 and successors 1966 • DOS/VS 1972 • DOS/VSE 1980s • VSE/SP late 1980s • VSE/ESA 1991 • z/VSE 2005 Michigan Terminal System 2 • OS/360 and successors