CP-67

CP-67
Name	CP-67
Developer	IBM
Family	IBM System/360
Released	1967
Discontinued	1972
Latest release version	CP/CMS
Marketing target	time-sharing
Operating system	CP/CMS
Platform	System/360 Model 67

CP-67 CP-67 was an influential virtual machine operating system developed for the System/360 Model 67 by IBM pioneering concepts in time-sharing, virtual memory, multiprocessing, and operating system design. It acted as a research and production platform that informed later commercial systems and academic projects across Bell Labs, MIT, Stanford University, and University of Cambridge. CP-67's design decisions shaped the evolution of VM (operating system family), influenced projects at DEC, Multics, and intersected with initiatives funded by the Advanced Research Projects Agency.

Overview

CP-67 provided a control program that created multiple isolated virtual machines on a single System/360 Model 67 instance, enabling simultaneous execution of diverse workloads from institutions such as IBM Research, Harvard University, Carnegie Mellon University, and Princeton University. It was paired with the Cambridge Monitor System, later known as CMS (Cambridge Monitor System), offering interactive user sessions akin to environments later seen in Unix and TENEX. CP-67 was notable for operational deployments at sites like Stanford Linear Accelerator Center and Lawrence Livermore National Laboratory and for research collaborations with National Physical Laboratory.

Architecture and Features

The architecture of CP-67 centered on hardware-assisted virtual memory provided by the System/360 Model 67's Dynamic Address Translation facility, enabling each virtual machine to have its own isolated address space comparable to physical machines used by entities like National Institutes of Health and NASA. Key features included a hypervisor-like control program implementing privilege separation reminiscent of later Xen hypervisor designs, an interactive command environment modeled after CTSS traditions, and support for batch and interactive jobs used at Bell Labs and MITRE Corporation. CP-67 incorporated scheduling strategies informed by contemporaneous research at University of California, Berkeley and provided device emulation for peripherals common at Los Alamos National Laboratory.

Development and History

Development began in the mid-1960s at IBM Cambridge Scientific Center with influences from projects at MIT Project MAC and collaborations with researchers from Stanford University and Princeton University. Early milestones included demonstrations at conferences hosted by Association for Computing Machinery and deployments that paralleled work on Multics at MIT Lincoln Laboratory. CP-67 evolved through iterative releases incorporating findings from experimental use at SRI International and operational feedback from companies like General Electric and Hewlett-Packard. Its lifecycle overlapped with policy debates in United States Department of Defense procurement and with academic computing center expansions across Ivy League institutions.

Performance and Use Cases

CP-67's performance characteristics suited it to research, academic, and commercial time-sharing use cases: interactive development for users from University of Illinois Urbana-Champaign, transactional processing for organizations like American Airlines and batch scientific workloads for facilities such as Brookhaven National Laboratory. Benchmarks of the era compared CP-67 installations to contemporaneous systems from DEC and studies published through ACM SIGOPS and IEEE venues. Use cases included language development for FORTRAN and ALGOL, interactive text editing influenced by tools at Bell Labs, and remote terminal access similar to services later offered by Comcast-era providers.

Compatibility and Integration

CP-67 integrated with IBM hardware ecosystems and supported emulation of System/360 instruction sets used by software from vendors including Microsoft-era predecessors, academic compilers from Stanford Artificial Intelligence Laboratory, and database experiments contemporaneous with IBM System/3 research. Integration efforts involved linking with networking research at ARPA and testbeds connecting to nodes at University College London and California Institute of Technology. The software facilitated interoperability with job control languages established by IBM and with peripheral standards used in installations at AT&T and Honeywell.

Security and Reliability

CP-67 advanced isolation and protection mechanisms by using hardware-assisted address translation to enforce separation among virtual machines, paralleling concepts later formalized in security analyses at RAND Corporation and National Security Agency-funded research. Reliability practices included checkpointing and restart procedures deployed at critical facilities like Lawrence Berkeley National Laboratory and rigorous testing protocols modeled after processes from Bell Labs and IBM Research. These practices informed later formal verification and security-hardening efforts in systems developed at Carnegie Mellon University's Software Engineering Institute.

Legacy and Influence

CP-67's legacy persisted through its direct descendant systems in the VM (operating system family), its influence on the architecture of commercial hypervisors such as designs explored at Microsoft Research and VMware, and its conceptual impact on academic projects like Multics and modern virtualization efforts at Xen Project and KVM. Historical retrospectives at institutions including Computer History Museum, publications by IEEE Annals of the History of Computing, and curricula at Massachusetts Institute of Technology trace CP-67's role in shaping virtualization, time-sharing norms, and operating system pedagogy across computing centers worldwide.

Category:IBM operating systems