IBM System/38

IBM System/38
Name	IBM System/38
Developer	IBM
Release	1979
Discontinued	1985
Cpu	CISC single-chip and microcode-controlled processors
Memory	up to several megabytes
Os	CPF
Predecessor	IBM System/3
Successor	IBM AS/400

IBM System/38 The IBM System/38 was a midrange computer platform introduced by IBM in 1979 designed for commercial data processing and application hosting. It combined novel hardware features and an object-based operating environment to support business applications for corporations such as General Motors, Bank of America, AT&T, and Procter & Gamble. The platform influenced subsequent IBM systems and research efforts across Hursley, Poughkeepsie, and Endicott development centers.

Overview and Architecture

The System/38 architecture emphasized an integrated design blending processor microcode, hardware-supported security, and an object-oriented execution environment developed by teams at IBM Research and IBM systems labs including IBM Rochester and IBM Hursley. It introduced features such as single-level store, hardware-enforced object authority, and a capability-like addressing model influenced by work from Edsger W. Dijkstra-era thinking and contemporaneous projects at Bell Labs and MIT. The hardware used microcode to implement a high-level instruction set enabling portability across processor implementations, echoing concepts later discussed at ACM SIGPLAN conferences and in papers by researchers affiliated with University of California, Berkeley and Carnegie Mellon University.

Hardware Components

System/38 systems shipped in rack and cabinet configurations with central processors, integrated storage controllers, and optional peripheral subsystems produced or supported in coordination with IBM manufacturing sites in Poughkeepsie and Endicott. Key components included processor units implementing microcoded control similar in principle to designs from DEC and influenced by microprogramming work at Manchester University. Disk and tape subsystems interoperated with IBM storage families such as devices used by IBM 3380 and later compatible peripherals. Memory management and I/O were tightly coupled to the system’s single-level store concept and to hardware security features reminiscent of capability architectures studied at Stanford University and Cornell University.

System Software and Object-Based Design

The System/38 Control Program Facility (CPF) implemented an object-based operating environment where files, programs, devices, and user profiles were explicit objects with associated authorities — a departure from file-and-process models used by UNIX, VMS, and MVS. CPF’s object paradigms were informed by research from Xerox PARC, University of Cambridge systems work, and by designers who later contributed to projects at Microsoft Research and Sun Microsystems. System/38 supported a serialized job control language and interactive facilities that linked to transactional middleware used by enterprises like Coca-Cola and Honeywell.

Programming Model and Languages

Programming on the System/38 utilized languages and tools such as RPG II, COBOL, and PL/I, along with higher-level compilers that targeted the system’s microcoded instruction set. IBM and third-party vendors delivered compilers and utilities compatible with development processes familiar to teams from E. I. du Pont de Nemours and Company and AT&T Bell Labs. The object-based execution model affected calling conventions and runtime behavior in ways studied by academics at Princeton University and Massachusetts Institute of Technology, and it presaged managed runtime ideas later embodied in environments like Java Virtual Machine discussions and Smalltalk systems.

Commercial History and Market Impact

Introduced amid competition from vendors such as Digital Equipment Corporation, Unisys, and Honeywell, the System/38 targeted medium-sized enterprises and departments within large corporations including Ford Motor Company and Bank of America. Market uptake influenced IBM’s strategy in the 1980s, prompting cross-development with initiatives at IBM Rochester and decisions that led to the consolidation into the AS/400 product line announced in 1988. The platform’s commercial trajectory intersected with industry trends covered in reports by firms like Gartner and IDC, and with procurement decisions by institutions including Walmart and Citibank.

Legacy and Influence on Modern IBM Systems

The System/38’s single-level store, object-based security, and microcode-driven portability informed the architecture of the IBM AS/400 and later IBM i implementations maintained by teams at IBM Rochester and IBM Hursley. Concepts originating on the System/38 influenced research at IBM Research labs, and echoed in enterprise platform strategy discussions involving Red Hat partnerships and cloud-era transitions managed by IBM Cloud groups. Academic citations and industrial case studies at Stanford University and Columbia University trace lineage from System/38 design decisions to modern managed runtimes, database integrations, and platform security practices used by Amazon Web Services customers migrating legacy workloads.

Category:IBM computers Category:Computer hardware introduced in 1979