VM/CMS

VM/CMS
Name	VM/CMS
Developer	International Business Machines Corporation
Family	IBM System/370 and successors
Released	1972 (VM 370)
Latest release	z/VM (successor)
Written in	PL/I, Assembler
Kernel type	Hypervisor (Type 1)
License	Proprietary

VM/CMS VM/CMS is a virtualization and interactive computing environment developed by International Business Machines Corporation for mainframe systems. It introduced time-sharing, guest operating system support, and a single-user interactive subsystem that influenced later virtualization and cloud concepts in computing history. The system evolved alongside IBM hardware lines and intersected with developments involving organizations and projects worldwide.

History

VM/CMS originated in the context of IBM's product developments and research initiatives during the late 1960s and early 1970s, influenced by work at IBM Cambridge Scientific Center, IBM Research - Yorktown Heights, and the design efforts that produced System/360 and System/370. Early milestones involved projects such as the Cambridge Scientific Center CP-67 experiment and internal teams connected to Project MAC and collaborations with institutions like Massachusetts Institute of Technology and Stanford Research Institute. Commercial releases aligned with announcements at venues like National Computer Conference and were contemporaneous with competing systems from Control Data Corporation, Honeywell, and General Electric.

Throughout the 1970s and 1980s VM/CMS development paralleled initiatives such as MVS, DOS/VS, and the broader IBM mainframe roadmap including System/370 Extended Architecture evolution and standards from American National Standards Institute. Influential users and adopters included University of California, Berkeley, Massachusetts Institute of Technology, Stanford University, Princeton University, and corporations like American Express, AT&T, and General Electric. The VM lineage later converged with IBM programs leading to z/VM and integration with virtualization strategies adopted by enterprises represented at Society for Industrial and Applied Mathematics conferences and industry bodies like AFIPS.

Architecture and Components

The architecture integrated a virtualization monitor (hypervisor) layer known as CP with a conversational monitor subsystem known as CMS; CP managed resources and created virtual machines while CMS provided interactive services. Design concepts referenced work on hardware facilities such as System/370 architecture enhancements including support for virtual storage and I/O channels used in IBM products like IBM 3033 and IBM 3090. Key components interfaced with IBM products and standards including SNA, VTAM, and products in the z/Architecture family.

VM/CMS employed a modular structure with components for CPU virtualization, storage virtualization, device emulation (e.g., disk and tape represented for guests), and system control facilities integrated with tooling used by organizations like National Institutes of Health and Federal Reserve System for operations. Subsystems and utilities included file systems influenced by conventions used by institutions such as Bell Labs and tools developed or extended by entities like Computer History Museum contributors and mainframe user groups such as Guide Share.

Operating Concepts and User Interface

The system introduced per-user single-address-space interactive environments and command-driven interfaces that resembled later shells and influenced workstation interfaces at laboratories including MIT Laboratory for Computer Science and Xerox PARC. User interaction models included the use of virtual consoles, file concepts, and utilities employed by research groups at Lawrence Livermore National Laboratory and Los Alamos National Laboratory.

Operational paradigms integrated with system management practices from enterprises such as General Motors and United States Postal Service, and administration tools paralleled those found in environments like UNIX deployments at Bell Labs and University of California, Berkeley. Interfaces were used via terminals such as those from DEC and terminal emulators developed by firms like HCL Technologies and Fujitsu to connect to mainframe hosts.

Programming and Application Support

Programming support included system APIs, macro services, and languages used across academic and industrial sites including PL/I, Assembly language, COBOL, and FORTRAN. Development tools and compilers came from IBM toolchains and vendors such as Microsoft (early tooling collaborations), Rational Software-style processes, and academic compilers from Stanford University and Massachusetts Institute of Technology.

Application areas encompassed batch processing, interactive development, database access with technologies like IMS and DB2 in later integrations, and networking via protocols supported by IBM SNA and gateways to systems like DEC VAX and Sun Microsystems servers. Third-party software from vendors including CA Technologies, BMC Software, and RCA-era tools were adapted to run within virtual machines for testing, development, and production workloads used by corporations like Citi and Barclays.

Performance, Scalability, and Virtualization Features

VM/CMS leveraged virtual storage features in hardware platforms including System/370, ESA/390, and later z/Architecture to provide isolation and resource multiplexing. Performance optimizations included dispatching algorithms and paging strategies comparable to research from University of Toronto and Carnegie Mellon University; scalability was demonstrated on chamber deployments running multiple guests on processors such as IBM z196 and IBM z14 families.

Virtualization features anticipated cloud computing attributes later adopted by providers like Amazon Web Services, Google Cloud Platform, and Microsoft Azure in concepts such as multitenancy, resource pooling, and live migration research influenced by studies presented at conferences like ACM SIGOPS and USENIX. Benchmarking and capacity planning used methodologies promoted by organizations such as SPEC and IEEE working groups.

Adoption, Use Cases, and Legacy Impact

Adoption spanned universities, governments, and enterprises including NASA, Department of Defense (United States), Citigroup, and BP for workloads from transaction processing to research computing. Use cases included software development sandboxes, production consolidation, and time-sharing services provided to academic consortia like CERN and national labs.

The legacy influenced modern hypervisors such as those from VMware, Inc., Xen Project, and KVM and contributed concepts found in container orchestration technologies developed by Docker, Inc. and Kubernetes-era ecosystems. Historians and curators at institutions like Computer History Museum and Smithsonian Institution document VM/CMS influence alongside biographies of engineers connected to IBM programs archived at Charles Babbage Institute and repositories such as IEEE Computer Society collections.

Category:IBM mainframe software