To understand why the iSeries (and its predecessors) occupies such a legendary status in computing, we have to look past the beige (and later black) metal boxes. The "magic" of this lineage lies in its architecture—specifically, a design philosophy that prioritized longevity and integration above all else.
1. The Architectural Departure: System/38
To understand the iSeries, you have to understand the System/38, released in 1978. While the rest of the world was building computers where software was tightly coupled to the physical wiring of the processor, IBM’s Rochester engineers did something radical. They decided that the hardware shouldn't matter to the application.
They achieved this through two primary pillars: Technology Independent Machine Interface (TIMI) and Single-Level Storage (SLS).
The "Great Insulator": TIMI
TIMI is a software layer that sits between the operating system/applications and the hardware. In a standard PC, if you change from an Intel processor to an ARM processor, your software breaks because the "instruction set" is different.
On an iSeries, the compiler doesn't produce "machine code" that the CPU understands directly. Instead, it produces an intermediate form of code.
-
When the code runs, the system translates it to the specific hardware's requirements.
-
If IBM releases a brand-new processor ten years later, the system simply "re-translates" the existing programs during the migration.
This is why companies can still run code written in 1982 on a 2024 Power10 server without having the original source code. It is arguably the greatest feat of "future-proofing" in the history of the Silicon Age.
2. Single-Level Storage (SLS)
In a Windows or Linux environment, a programmer has to worry about "files" and "memory." You move a file from the disk (permanent storage) into RAM (temporary memory) to work on it.
The iSeries architecture treats the entire system's disk space and RAM as one giant, flat address space.
-
The Benefit: The OS handles the movement of data between disk and RAM automatically.
-
The Result: It eliminates the need for manual disk management and "defragging." It also makes the system incredibly resilient to fragmentation, as the OS scatters data across all available disk arms to maximize performance.
3. The World’s First Database Machine
Perhaps the most "iSeries" trait of all is that it doesn't have a database; it is a database.
On a Windows server, you install SQL Server. On a Linux server, you install Oracle or MySQL. On the iSeries, DB2 is integrated into the microcode of the operating system itself.
-
Security: Because the database is part of the OS, you cannot "lose" a file or have a database crash while the OS stays up. They are one and the same.
-
Object-Oriented Integrity: In the iSeries world, everything is an "object." You cannot treat a data file like an executable program. This architectural wall is the reason why the iSeries has remained virtually immune to the viruses and malware that plague traditional file-based systems.
4. The 1995 "Brain Transplant"
The true test of this architecture came in the mid-90s. IBM decided to move from the old CISC (Complex Instruction Set Computing) 48-bit processors to the new RISC (Reduced Instruction Set Computing) 64-bit PowerPC processors.
In any other environment, this would have been a "platform migration" costing millions and taking years. For iSeries users, it was a "Save/Restore" operation. Because of TIMI, the programs didn't know the hardware had changed. They simply re-encapsulated to the new 64-bit instruction set upon the first execution. This event proved that the Rochester engineers had successfully decoupled software from the constraints of time and hardware.