IBM System/390

IBM System/390
Name	IBM System/390
Developer	IBM
Family	System/390/zSeries
Released	1990
Discontinued	2000s
Predecessor	IBM System/370
Successor	zSeries
Type	Mainframe

IBM System/390 The IBM System/390 was a family of mainframe computers introduced by IBM in 1990, representing a line of high-end enterprise servers that continued a lineage from the IBM System/370 and influenced the later zSeries and z/Architecture. It served major institutions in finance, banking, insurance, telecommunications, and government sectors, supporting mission-critical workloads with emphasis on throughput, availability, and virtualization. The platform integrated innovations in multiprocessing, channel I/O, and virtualization that built upon technologies developed across Poughkeepsie, New York, Burlington, Vermont, and other IBM research and development sites.

Overview and Development

The System/390 emerged from design efforts within IBM during the late 1980s as a response to demands from customers such as Bank of America, Citibank, Deutsche Bank, and large telecommunications carriers for greater consolidation and virtualization. Development teams collaborated with groups in Hursley, Poughkeepsie, and Böblingen to integrate chip advancements influenced by research at IBM Research and standards work involving ANSI and ISO. Announced in 1990, the System/390 family formalized upgrades to packaging, cooling, and channel architecture while remaining binary compatible with workloads written for IBM System/370. The product line evolved through roadmap milestones that led to the adoption of expanded memory addressing and symmetric multiprocessing prior to the transition to the zSeries in the late 1990s.

Architecture and Instruction Set

The System/390 architecture preserved the 32-bit instruction set architecture lineage of IBM System/370 while introducing extensions that anticipated future 64-bit developments embodied in z/Architecture. Its core featured a register-based model with sixteen general-purpose registers and an instruction repertoire used by operating systems such as z/OS, MVS, and VM/CMS. The architecture supported channel I/O via IBM Channel I/O, multiprocessing coordination through symmetric multiprocessing designs, and virtualization primitives used by VM/ESA and related hypervisors. Microcode-controlled features allowed firmware updates and architectural fixes, paralleling techniques also used by Intel in microprocessor control and by DEC in its VAX series. System/390 included support for decimal arithmetic aligned with standards employed in financial services and compatibility facilities for legacy datasets derived from mainframe-era standards.

Hardware Models and Configurations

System/390 encompassed a range of models from entry-class processors to large-scale multiprocessing systems deployed in datacenter complexes owned by organizations like JPMorgan Chase and HSBC. Configurations combined central processors, channel subsystems, and peripheral control units interoperable with devices from vendors including StorageTek and Hitachi Data Systems. Cabinets housed processors, memory banks, and specialized co-processors; models used CISC microarchitectures implemented in CMOS technology influenced by semiconductor fabrication advances at GlobalFoundries and IBM Microelectronics. I/O topologies used ESCON and later FICON channel interfaces, with connectivity to storage arrays, tape libraries, and network gateways common in deployments for stock exchanges and airline reservation systems.

Operating Systems and Software Ecosystem

A vibrant software ecosystem surrounded System/390, with flagship operating systems such as MVS (later z/OS), VM/ESA (virtual machine family), and VSE/ESA serving distinct markets like banking, airline systems, and government agencies. Middleware vendors like CA Technologies, BMC Software, and Tivoli provided systems management, while database platforms including IBM DB2, Oracle Database, and transaction managers such as CICS and IMS supported enterprise applications. Development and porting efforts involved toolchains and languages like COBOL, PL/I, Assembler (IBM System/360) programming, and later support for Java (programming language) on mainframe runtimes. Ecosystem partnerships with systems integrators such as Accenture and Capgemini helped migrate legacy workloads and implement high-availability architectures.

Performance, Reliability, and Scalability

System/390 systems emphasized throughput, fault tolerance, and online serviceability used by mission-critical operators including SWIFT and national clearing systems. Hardware redundancy, dynamic resource allocation, and channel failover mechanisms reduced planned and unplanned downtime, aligning with service-level expectations in financial services and air traffic control environments. Performance benchmarking drew on industry standards and workload characterizations similar to those later standardized by SPEC and academic studies from institutions like MIT and Stanford University. Scalability strategies included logical partitioning and clustering that presaged technologies found in later distributed computing platforms from vendors like Sun Microsystems and HP.

Legacy and Influence on z/Architecture

The System/390 lineage directly informed the introduction of the 64-bit z/Architecture in the zSeries era, carrying forward concepts in virtualization, channel I/O, and enterprise-grade reliability into modern mainframe ecosystems used by Amazon Web Services partners and cloud integrators. Architectural lessons from System/390 shaped subsequent designs in processor microcode, I/O virtualization, and large-scale system management adopted by IBM and observed by competitors such as Fujitsu and Unisys. Software continuity ensured that decades of enterprise applications written for System/390 could be migrated to z/Architecture platforms with minimal rewrites, preserving investment for institutions including IRS (United States) systems, major retail chains, and national healthcare databases. As a transitional architecture, System/390 stands as a pivotal node connecting mid-20th-century mainframe heritage to 21st-century enterprise computing.

Category:IBM mainframes Category:Computer history