• The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
Menu
  • The Four Hundred
  • Subscribe
  • Media Kit
  • Contributors
  • About Us
  • Contact
  • In Mainframe We Antitrust: System/360 Compels System/3

    April 14, 2014 Timothy Prickett Morgan

    The mainframe, as first embodied in the System/360 and carried forward to the System z, celebrated its 50th birthday last week. And while we technically do not cover the mainframe in this publication, the very fact that IBM created the mainframe and was paranoid about losing this fast-growing and lucrative business is perhaps the very reason that the IBM i platform as we know it exists.

    I am not going to go through the entire history of the IBM mainframe line. So many others did that last week, and that is all interesting and fun reading. Over at EnterpriseTech, I reminded readers that the System/360 was not just a revolutionary machine embodying some of the core ideals of, well, enterprise technology, that we think of as normal, but it was a system with business practices that were created under the constraints of the 1956 Consent Decree that IBM signed with the U.S. Department of Justice to end a lawsuit from 1952 accusing IBM of monopolistic control of the punch card tabulation machine market. It is intuitively obvious that IBM had a monopoly back then, and with the System/360, the wild popularity of the mainframe gave IBM much more control of a much larger market. In fact, it was the mainframe that made IBM the blue chip stock that it has been since 1960s and that turned IBM into a giant of computing, manufacturing, research, and sales. IBM didn’t have to do marketing back then so much. People were lining up for these machines, which had a common set of operating systems and application runtimes and which allowed for third-party peripherals and third-party financing, among many other innovations.

    Here’s the fun bit. IBM was always worried that its precious mainframe business would be broken up in some way if the Antitrust Division or the U.S. Federal district judge David Edelstein, who presided over the IBM case, decided that IBM was misbehaving. And so, when IBM decided to go into the midrange business, it did so with the System/3, a box that was incompatible with the System/360–thus violating the core tenet of the venerable mainframe. The System/3 hailed from Rochester, Minnesota, nowhere near the upstate New York stomping grounds of the punch card and mainframe businesses, although that was close to supercomputer makers Control Data and Cray and some very innovative computer science programs at the Big Ten schools.

    Yes, I know that IBM had Report Program Generator on earlier mainframes as well as the System/360 and some of its follow-ons, but I just wanted to point this out: If IBM was not paranoid about protecting the mainframe, you would all have been COBOL and CICS programmers and your companies would have been paying at least twice as much per transaction over the many decades years.



                         Post this story to del.icio.us
                   Post this story to Digg
        Post this story to Slashdot

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    Tags:

    Sponsored by
    Midrange Dynamics North America

    Want to deliver DevOps on IBM i?

    DevOps enables your IBM i development teams to shorten the software development lifecycle while delivering features, fixes, and frequent updates that are closely aligned with business objectives. Flexible configuration options within MDChange make it easy to adapt to new workflow strategies and policies as you adopt DevOps practices across your organization.

    Learn More.

    Share this:

    • Reddit
    • Facebook
    • LinkedIn
    • Twitter
    • Email

    IBM Names 11 Fellows As Analytics Dominates Discussion Oracle Ties In-Memory JDE Enhancement to Own Hardware

    Leave a Reply Cancel reply

Volume 24, Number 13 -- April 14, 2014
THIS ISSUE SPONSORED BY:

Profound Logic Software
LANSA
ASNA
Linoma Software
WorksRight Software

Table of Contents

  • Big Blue Launches IBM i 7.1 TR8 As 7.2 Looms
  • Heartbleed, OpenSSL, and IBM i: What You Need to Know
  • Life In Javaland
  • Mad Dog 21/21: Who Says Elephants Can’t Die?
  • IBM Schedules Power Systems Event For April 28
  • Reader Feedback On Penton Media IBM i Shutdown And Women In IT
  • Oracle Schemes Schema Protection in JDEREF Website Shutdown
  • In Mainframe We Antitrust: System/360 Compels System/3
  • More IBM Job Losses Expected This Week
  • Education Foundation Airlifts Students To COMMON

Content archive

  • The Four Hundred
  • Four Hundred Stuff
  • Four Hundred Guru

Recent Posts

  • AI Is Coming for ERP. How Will IBM i Respond?
  • The Power And Storage Price Wiggling Continues – Again
  • LaserVault Adds Multi-Path Support To ViTL
  • As I See It: Spacing Out
  • IBM i PTF Guide, Volume 27, Numbers 34, 35, And 36
  • The Power11 Transistor Count Discrepancies Explained – Sort Of
  • Is Your IBM i HA/DR Actually Tested – Or Just Installed?
  • Big Blue Delivers IBM i Customer Requests In ACS Update
  • New DbToo SDK Hooks RPG And Db2 For i To External Services
  • IBM i PTF Guide, Volume 27, Number 33

Subscribe

To get news from IT Jungle sent to your inbox every week, subscribe to our newsletter.

Pages

  • About Us
  • Contact
  • Contributors
  • Four Hundred Monitor
  • IBM i PTF Guide
  • Media Kit
  • Subscribe

Search

Copyright © 2025 IT Jungle