The IBM System/36 and the IBM AS/400 (Application System/400) are two of the most successful midrange computers in IBM’s history, but they represent very different eras and philosophies. The System/36 was the immediate predecessor in many markets, while the AS/400 was designed as its long-term successor. Below is a detailed side-by-side comparison of their histories, architectures, target markets, and lasting impact.
Table of Contents
1. Historical Timeline and Development
| Aspect | IBM System/36 (S/36) | IBM AS/400 (Application System/400) |
|---|---|---|
| Announcement | May 1983 | June 21, 1988 (available August 1988) |
| General Availability | July 1983 | August 1988 |
| Replacement For | System/32 and older 1130/360 models | System/36 and System/38 (dual replacement) |
| Development Project | “Cheetah” project (started late 1970s) | “Silverlake” project (started December 1985) after the failed “Fort Knox” project |
| Design Goal | Low-cost, easy-to-use system for small businesses | Unified, future-proof midrange platform with extreme backward compatibility |
| End of Production | 1994 (last models) | Original hardware discontinued ~2013; platform lives on as IBM i |
| Peak Installations | ~300,000 units by 1990 | ~500,000 units shipped by 1997; millions of applications still running today |
The System/36 was introduced to fill the gap left by the aging System/32 and to compete with smaller systems from competitors like DEC, HP, and Wang. It was a great success, but by the mid-1980s IBM realized it needed a single, long-lived platform to replace both the S/36 and the more advanced System/38. That led to the creation of the AS/400.
2. Architecture and Technical Comparison
| Feature | System/36 (S/36) | AS/400 (and later IBM i) |
|---|---|---|
| Processor Architecture | 16-bit proprietary (SCP processor) | 48-bit CISC (IMPI) → 64-bit PowerPC/POWER family (1995 onward) |
| Operating System | SSP (System Support Program) – simple, menu-driven | OS/400 (later i5/OS, now IBM i) – object-based, integrated |
| Memory Model | Traditional segmented memory (64 KB segments) | Single-level store (64-bit virtual address space) |
| Programming Model | Procedural, RPG II/III, COBOL, BASIC, assembly | Object-oriented, RPG IV/ILE, COBOL, C, C++, Java, PASE, etc. |
| Database | Flat files, indexed sequential (S/36-style) | Integrated relational database (Db2 for i) |
| Backward Compatibility | Good within S/36 family, but limited to System/32 | Exceptional: 1988 applications still run on modern IBM i (2025) |
| Hardware Abstraction | Minimal; applications tied to hardware | Technology Independent Machine Interface (TIMI) – full abstraction |
| Security Model | Basic user profiles and passwords | Object-based authority, five security levels (up to C2) |
| Virtualization | None | LPAR (logical partitioning) since 1999, later KVM and containers |
| Networking | SNA, Token-Ring, later TCP/IP add-ons | Native TCP/IP, SNA, later Ethernet, cloud integration |
The most revolutionary aspect of the AS/400 was its Technology Independent Machine Interface (TIMI). This allowed applications compiled for the original 48-bit IMPI processors to run unchanged on 64-bit POWER processors decades later. The System/36 had no such abstraction, so applications had to be recompiled or rewritten when moving to new hardware.
3. Market Positioning and Target Audience
| Aspect | System/36 | AS/400 (and IBM i) |
|---|---|---|
| Primary Market | Small businesses, departments, first-time computer users | Small-to-medium businesses, mid-size enterprises, large companies |
| Typical Installation | 1–30 users, often in offices with minimal IT staff | 1–hundreds of users, mission-critical applications |
| Ease of Use | Very easy; menu-driven, “turnkey” solutions | Still user-friendly but far more powerful and scalable |
| Price Range (1980s) | $10,000–$80,000 | $20,000–$500,000+ (wide range of models) |
| Typical Software | MAPICS, BPCS, custom RPG applications | MAPICS, JD Edwards, BPCS, SAP R/3, custom RPG/COBOL |
The System/36 was the entry-level system that introduced thousands of companies to IBM midrange computing. Many of those customers later migrated to the AS/400 because it could run System/36 applications with minimal or no changes (via the System/36 Environment and later the 36/38 compatibility layer).
4. Migration Path from System/36 to AS/400
IBM made the transition remarkably smooth:
- System/36 Environment (introduced with early AS/400 models) allowed S/36 programs to run natively under OS/400.
- Automatic conversion tools moved RPG II programs to RPG III/IV.
- Data migration was straightforward because both systems used similar file structures.
As a result, many companies that started on a System/36 in the 1980s still run the same applications today on modern IBM Power Systems running IBM i 7.6 (2025).
5. Longevity and Current Status
| Aspect | System/36 | AS/400 / IBM i |
|---|---|---|
| Last Hardware Shipment | 1994 | Original AS/400 hardware discontinued ~2013 |
| Current Platform | None (emulation only) | IBM i on IBM Power Systems (Power10, Power11 in preview) |
| Active Installations | Very few (mostly emulated) | Tens of thousands of production systems worldwide |
| Support Status | Ended decades ago | IBM i 7.5 support until ~2030; 7.6 released 2025 |
| Modern Use Cases | Mostly legacy or hobbyist emulation | Mission-critical ERP, banking, manufacturing, cloud |
While the System/36 is now largely a historical footnote (though still fondly remembered by many midrange veterans), the AS/400’s architecture lives on as IBM i. The same core principles—object-based design, single-level store, and TIMI—continue to deliver unmatched reliability and backward compatibility.
Summary: Key Takeaways
- The System/36 was a highly successful, easy-to-use system for small businesses in the 1980s, but it was fundamentally limited by its 16-bit architecture and lack of long-term abstraction.
- The AS/400 was deliberately designed to be the “last midrange system you’ll ever need,” with a future-proof architecture that has kept it relevant for nearly four decades.
- The AS/400 inherited the System/36’s customer base and ran their applications, allowing thousands of companies to grow without rewriting their software.
- Today, while the System/36 is extinct, its direct descendant—the IBM i operating system—continues to power critical business workloads on the latest IBM Power hardware.
In essence, the System/36 was the stepping stone; the AS/400 was the bridge that carried those businesses into the modern era—and it’s still carrying them today.
- https://en.wikipedia.org/wiki/IBM_System/36 Primary source for System/36 history: announcement (May 16, 1983), models (5360, 5362, etc.), SSP operating system features (multiprogramming, job queues, security), end of marketing (~2000), and migration notes to AS/400.
- https://wiki.midrange.com/index.php/System/36 Midrange community wiki detailing System/36 timeline, models, SSP details, reliability (“bulletproof” uptime), and transition challenges to AS/400, including lack of object-code compatibility.
- https://en.wikipedia.org/wiki/IBM_AS/400 Comprehensive overview of AS/400 announcement (June 1988), Silverlake project origins, architecture (TIMI, single-level store), processor evolution, and explicit compatibility features for System/36 (e.g., System/36 Environment requiring recompilation).
- https://www.ibm.com/history/as-400 Official IBM history page highlighting AS/400’s backward compatibility with System/36 applications, performance improvements (e.g., 45,000 transactions/hour vs. System/36), and market positioning.
- https://biztechmagazine.com/article/2017/08/ibms-system36-increased-personal-computing-power-small-businesses Article on System/36’s market impact, installations (~300,000 units), pricing, and succession by AS/400 (with ~200,000 AS/400 shipments by 1992).
- https://en.wikipedia.org/wiki/IBM_i Details on IBM i evolution, including System/36 Environment support in OS/400 (recompilation needed) and discontinuation of full SSP emulation (Advanced 36 Machine) after V4R4.
- https://public.dhe.ibm.com/systems/power/docs/systemi/v6r1/en_US/sc414731.pdf (IBM System/36 Environment Reference) Official IBM manual describing System/36 Environment on AS/400/OS/400, including device mapping, OCL/procedure support, and migration techniques.
- https://bitsavers.org/pdf/ibm/as400/GG24-3249-03_System-36_to_AS400_System_Migration_2nd_ed_199001.pdf IBM guide on migrating from System/36 to AS/400, covering tools for program conversion, data migration, and security mapping.
- https://wiki.midrange.com/index.php/SSP Explanation of System Support Program (SSP) features like DFU, SEU, SDA, and differences from OS/400.
- https://lansa.com/blog/application-modernization/ibm-i-modernization/ibm-i-vs-as400-how-are-they-different/ Overview of AS/400 as successor to System/36/System/38, runtime environment support, and ongoing IBM i compatibility.
