VM (operating system)

VM (often: VM/CMS) is a family of IBM virtual machine operating systems used on IBM mainframes System/370, System/390, zSeries, System z and compatible systems, including the Hercules emulator for personal computers.

z/VM

Developer	IBM
OS family	VM family
Working state	Current
Source model	1972–1986 Open source, 1977–present Closed source
Initial release	1972
Latest release	IBM z/VM V7.1 / October 16, 2018
Marketing target	IBM mainframe computers
Available in	English
Platforms	System/370, System/390, zSeries, IBM zEnterprise System
License	1972–1981 Public domain, 1976–present Proprietary
Official website	www.vm.ibm.com

The first version, released in 1972, was VM/370, or officially Virtual Machine Facility/370. This was a System/370 reimplementation of earlier CP/CMS operating system. Milestone versions included VM/SP.[1] The current version, z/VM, is still widely used as one of the main full virtualization solutions for the mainframe market.

The CMS usually coupled with VM in the name refers to the Conversational Monitor System, a single-user operating system developed to provide conversational time-sharing under VM.

Overview

The heart of the VM architecture is a control program or hypervisor called VM-CP (usually: CP; sometimes, ambiguously: VM). It runs on the physical hardware, and creates the virtual machine environment. VM-CP provides full virtualization of the physical machine – including all I/O and other privileged operations. It performs the system's resource-sharing, including device management, dispatching, virtual storage management, and other traditional operating system tasks. Each VM user is provided with a separate virtual machine having its own address space, virtual devices, etc., and which is capable of running any software that could be run on a stand-alone machine. A given VM mainframe typically runs hundreds or thousands of virtual machine instances. VM-CP began life as CP-370, a reimplementation of CP-67, itself a reimplementation of CP-40.

Running within each virtual machine is another, "guest" operating system. This might be:

• CMS ("Conversational Monitor System", renamed from the "Cambridge Monitor System" of CP/CMS). Its official name is VM-CMS (confusing, since VM is commonly called VM/CMS). Most virtual machines run CMS, a lightweight, single-user operating system. Its interactive environment is comparable to that of a single-user PC, including a file system, programming services, device access, and command-line processing. (While an earlier version of CMS was uncharitably described as "CP/M on a mainframe", the comparison is an anachronism; the author of CP/M, Gary Kildall, was an experienced CMS user.)
• A mainstream operating system. IBM's mainstream operating systems (i.e. the MVS or DOS/VSE families) can be loaded and run without modification. The VM hypervisor treats guest operating systems as application programs with exceptional privileges – it prevents them from using privileged instructions (those which would let applications take over the whole system or significant parts of it), but simulates privileged instructions on their behalf. Most mainframe operating systems terminate a normal application which tries to usurp the operating system's privileges.
• Another copy of VM. A "second level" instance of VM can be fully virtualized inside a virtual machine. This is how VM development and testing is done (a "second-level" VM can potentially implement a different virtualization of the hardware). This technique was used to develop S/370 software before S/370 hardware was available, and it has continued to play a role in new hardware development at IBM. The literature cites practical examples of virtualization five levels deep (see page 28 of VM and the VM Community). Levels of VM below the top are also treated as applications but with exceptional privileges.
• A copy of the mainframe version of AIX or Linux. In the mainframe environment, these operating systems often run under VM, and are handled like other guest operating systems. (They can also run as 'native' operating systems on the bare hardware.)
• A specialized VM subsystem. Several non-CMS systems run within VM-CP virtual machines, providing services to CMS users such as spooling, interprocess communications, and specialized device support. They operate "behind the scenes", extending the services available to CMS without adding to the VM-CP control program. By running in separate virtual machines, they receive the same security and reliability protections as other VM users. Examples include:
  • RSCS ("Remote Spooling and Communication Subsystem", aka VNET) – communication and information transfer facilities between virtual machines[2]
  • RACF ("Resource Access Control Facility") — a security system
  • GCS ("Group Control System"), which provides a limited simulation of the MVS API.
  • Shared File System (SFS), which organized shared files in a directory tree

Hypervisor interface

At one time, CMS was capable of running on a bare machine, as a true operating system (though such a configuration would be unusual). It now runs only as a guest OS under VM. This is because CMS relies on a hypervisor interface to VM-CP, to perform file system operations and request other VM services. This paravirtualization interface:

• Provides a fast path to VM-CP, to avoid the overhead of full simulation.
• Was first developed as a performance improvement for CP/CMS release 2.1, an important early milestone in CP's efficiency.
• Uses a non-virtualized, model-dependent machine instruction as a signal between CMS and CP: DIAG ("diagnose").

IBM coined the term "hypervisor" for the 360/65[3] and later used it for the DIAG handler of CP-67.

The Diagnose instruction ('83'x—no mnemonic) is a privileged instruction originally intended by IBM to perform "built-in diagnostic functions, or other model-dependent functions."[4] Under VM/370 it was repurposed for "communication between a virtual machine and CP." The instruction contains two four-bit register numbers, called Rx and Ry, which can "contain operand storage addresses or return codes passed to the DIAGNOSE interface," and a two-byte code "that CP uses to determine what DIAGNOSE function to perform."[5] A few of the available diagnose functions are listed below.

Hexadecimal code	Function
0008	"Virtual Console Function"—Execute a CP command
0020	General I/O—Execute any valid CCW chain on a tape or disk device
003C	Update the VM/370 directory
0058	3270 Virtual Console Interface—perform full-screen I/O on an IBM 3270 terminal
0060	Determine Virtual Machine Storage Size
0068	Virtual Machine Communication Facility (VMCF)

History

The early history of VM is described in the articles CP/CMS and History of CP/CMS. VM/370 is a reimplementation of CP/CMS, and was made available in 1972 as part of IBM's "System/370 Advanced Function" announcement (which added virtual memory hardware and operating systems to the System/370 series). Early releases of VM through VM/370 Release 6 continued in open source through 1981, and today are considered to be in the public domain. This policy ended in 1977 with the chargeable VM/SE and VM/BSE upgrades and in 1980 with VM/System Product (VM/SP). However, IBM continued providing updates in source form for existing code for many years, although the upgrades to all but the free base required a license. As with CP-67, privileged instructions in a virtual machine cause a program interrupt, and CP simulated the behavior of the privileged instruction.

VM remained an important platform within IBM, used for operating system development and time-sharing use; but for customers it remained IBM's "other operating system". The OS and DOS families remained IBM's strategic products, and customers were not encouraged to run VM. Those that did formed close working relationships, continuing the community-support model of early CP/CMS users. In the meantime, the system struggled with political infighting within IBM over what resources should be available to the project, as compared with other IBM efforts. A basic "problem" with the system was seen at IBM's field sales level: VM/CMS demonstrably reduced the amount of hardware needed to support a given number of time-sharing users. IBM was, after all, in the business of selling computer systems.

Melinda Varian provides this fascinating quote, illustrating VM's unexpected success:

The marketing forecasts for VM/370 predicted that no more than one 168 would ever run VM during the entire life of the product. In fact, the first 168 delivered to a customer ran only CP and CMS. Ten years later, ten percent of the large processors being shipped from Poughkeepsie would be destined to run VM, as would a very substantial portion of the mid-range machines that were built in Endicott. Before fifteen years had passed, there would be more VM licenses than MVS licenses.[6]

A PC DOS version that runs CMS on the XT/370 (and later on the AT/370) is called VM/PC. VM/PC 1.1 was based on VM/SP release 3.

When IBM introduced System/370 Extended Architecture on the 3081, customers were faced with the need to run a production MVS/370 system while testing MVS/XA on the same machine. IBM's solution was VM/XA Migration Aid, which used the new Start Interpretive Execution (SIE) instruction to run the virtual machine. SIE automatically handled some privileged instructions and returned to CP for cases that it couldn't handle. The Processor Resource/System Manager (PR/SM) of the later 3090 also used SIE. There were several VM/XA products before it was eventually supplanted by VM/ESA and z/VM.

VM's role changed within IBM when hardware evolution led to significant changes in processor architecture. Backward compatibility remained a cornerstone of the IBM mainframe family, which still uses the basic instruction set introduced with the original System/360; but the need for efficient use of the 64-bit zSeries made the VM approach much more attractive. VM was also utilized in data centers converting from DOS/VSE to MVS and is useful when running mainframe AIX and Linux, platforms that were to become increasingly important. The current z/VM platform has finally achieved the recognition within IBM that VM users long felt it deserved. Some z/VM sites run thousands of simultaneous virtual machine users on a single system. z/VM was first released in October 2000[7] and remains in active use and development.

IBM and third parties have offered many applications and tools that run under VM. Examples include RAMIS, FOCUS, SPSS, NOMAD, DB2, REXX, RACF, and OfficeVision. Current VM offerings run the gamut of mainframe applications, including HTTP servers, database managers, analysis tools, engineering packages, and financial systems.

CP commands

As of release 6, the VM/370 Control Program has a number of commands for General Users, concerned with defining and controlling the user's virtual machine. Lower-case portions of the command are optional[8]

Command	Description
#CP	Allows the user to issue a CP command from a command environment
ADSTOP	Sets an address stop to halt the virtual machine at a specific instruction
ATTN	Causes an attention interruption allowing CP to take control in a command environment
Begin	Continue or resume execution of the user's virtual machine, optionally at a specified address
CHange	Alter attributes of a spool file or files. For example, the output class or the name of the file can be changed, or printer-specific attributes set
Close	Closes an open printer, punch, reader, or console file and releases it to the spooling system
COUPLE	Connect a virtual channel-to-channel adapter (CTCA) to another
CP	Execute a CP command in a CMS environment
DEFine	Alter the current virtual machine configuration. Add virtual devices or change available storage size
DETach	Remove a virtual device or channel from the current configuration
DIAL	Connect your terminal to a logged-on multi-access virtual machine
DISConn	Disconnect your terminal while allowing your virtual machine to continue running
Display	Display virtual machine storage or (virtual) hardware registers
DUMP	Print a snapshot dump of the current virtual machine on the virtual spooled printer
ECHO	Set the virtual machine to echo typed lines
EXTernal	Cause an external interrupt to the virtual machine
INDicate	Display current system load or your resource usage
Ipl	IPL (boot) an operating system on your virtual machine
LINK	Attach a device from another virtual machine, if that machine's definition allows sharing
LOADVFCB	Specify a forms control buffer (FCB) for a virtual printer
LOGoff LOGout	Terminate execution of the current virtual machine and disconnect from the system
Logon Login	Sign on to the system
Message MSG	Send a one-line message to the system operator or another user
NOTReady	Cause a virtual device to appear "not ready"
ORDer	Reorder closed spool files by ID or class
PURge	Delete closed spool files for a device by class,m ID, or ALL
Query	Display status information for your virtual machine, or the "message of the day", or number or nbames of logged-in users
READY	Cause a device end interruption for a device
REQuest	Cause an interrupt on your virtual console
RESET	Clear all pending interrupts for a device
REWind	Rewind a real (non virtual) magnetic tape unit
SET	Set various attributes for your virtual machine, including messaging or terminal function keys
SLeep	Place your virtual machine in a "dormant state" indefinitely or for a specified period of time
SMsg	Send a one-line "special message" to another user
SPool	Set options for a spooled virtual device
STore	Alter the contents of registers or storage of your virtual machine
SYStem	Reset or restart your virtual machine or clear storage
TAg	Set a tag associated with a spooled device or file. The tag is usually used by VM's Remote Spooling Communications Subystem (RSCS) to identify the destination of a file
TERMinal	Set characteristics of your terminal
TRace	Start or stop tracing of specified virtual machine activities
TRANsfer	Transfer a spool file to or from another user
VMDUMP	Dump your virtual machine in a format readable by the Interactive Problem Control System (IPCS) program product

VM mascot

In the early 1980s, the VM group within SHARE (the IBM user group) sought a mascot or logo for the community to adopt. This was in part a response to IBM's MVS users selecting the turkey as a mascot (chosen, according to legend, by the MVS Performance Group in the early days of MVS, when its performance was a sore topic). In 1983, the teddy bear became VM's de facto mascot at SHARE 60, when teddy bear stickers were attached to the nametags of "cuddlier oldtimers" to flag them for newcomers as "friendly if approached". The bears were a hit and soon appeared widely.[9] Bears were awarded to inductees of the "Order of the Knights of VM", individuals who made "useful contributions" to the community.[10][11]

See also

• Time-sharing system evolution

References

1. Elliott, Jim (2004-08-17). "The Evolution of IBM Mainframes and VM" (PDF). Linux fo S/390 Linux for Big Iron. SHARE Session 9140. Retrieved 2007-10-21.
2. Creasy, op. cit., p. 483 — role of RSCS.
3. Gary R. Allred (1971). System/370 integrated emulation under OS and DOS (PDF). Spring Joint Computer Conference.
4. IBM Corporation (1987). IBM System/370 Principles of Operation (PDF). p. 10-5. Retrieved Aug 17, 2019.
5. IBM Corporation (Mar 1979). IBM Virtual Machine Facility/370:' System Programmer's Guide (PDF). pp. 182–206.4. Retrieved Aug 17, 2019.
6. Varian, op. cit., p. 30 – extent of VM use; more VM licenses than MVS licenses
7. "IBM: About the z/VM Operating System". IBM z/VM virtualization technology. Vm.ibm.com. Retrieved 2015-07-02.
8. IBM Corporation (August 1, 1979). IBM Virtual Machine Facility/370: CP Command Reference for General Users (PDF). Retrieved Aug 15, 2019.
9. "Gallery of VM web GIFs". IBM z/VM site. Archived from the original on October 18, 2006.
10. Varian, op. cit., p. 2 – the teddy bear story
11. "Explain "official VM teddy"". Mr. Alan J. Flavell. Alanflavell.org.uk. Retrieved 2015-07-02.

External links

VM sources

• Bob DuCharme, Operating Systems Handbook, Part 5: VM/CMS
  – a fairly detailed user's guide to VM/CMS
• E. C. Hendricks and T. C. Hartmann, "Evolution of a Virtual Machine Subsystem", IBM Systems Journal Vol. 18, pp. 111–142 (1979)
  – RSCS design and implementation
• IBM Corporation, IBM Virtual Machine Facility/370 Introduction, GC20-1800, (1972)
  – the original manual

Primary CP/CMS sources

• R. J. Creasy, "The origin of the VM/370 time-sharing system", IBM Journal of Research & Development, Vol. 25, No. 5 (September 1981), pp. 483–90, PDF
  ― perspective on CP/CMS and VM history by the CP-40 project lead, also a CTSS author
• E.W. Pugh, L.R. Johnson, and John H. Palmer, IBM's 360 and early 370 systems, MIT Press, Cambridge MA and London, ISBN 0-262-16123-0
  ― extensive (819 pp.) treatment of IBM's offerings during this period; the limited coverage of CP/CMS in such a definitive work is telling
• Melinda Varian, VM and the VM community, past present, and future, SHARE 89 Sessions 9059–61, 1997;
  ― an outstanding source for CP/CMS and VM history

Additional CP/CMS sources

• R. J. Adair, R. U. Bayles, L. W. Comeau and R. J. Creasy, A Virtual Machine System for the 360/40, IBM Corporation, Cambridge Scientific Center Report No. 320‐2007 (May 1966)
  ― a seminal paper describing implementation of the virtual machine concept, with descriptions of the customized CSC S/360-40 and the CP-40 design
• International Business Machines Corporation, CP-67/CMS, Program 360D-05.2.005, IBM Program Information Department (June 1969)
  ― IBM's reference manual
• R. A. Meyer and L. H. Seawright, "A virtual machine time-sharing system," IBM Systems Journal, Vol. 9, No. 3, pp. 199–218 (September 1970)
  ― describes the CP-67/CMS system, outlining features and applications
• R. P. Parmelee, T. I. Peterson, C. C. Tillman, and D. J. Hatfield, "Virtual storage and virtual machine concepts," IBM Systems Journal, Vol. 11, No. 2 (June 1972)

Background CP/CMS sources

• F. J. Corbató, et al., The Compatible Time-Sharing System, A Programmer’s Guide, M.I.T. Press, 1963
• F. J. Corbató, M. Merwin-Daggett, and R. C. Daley, "An Experimental Time-sharing System," Proc. Spring Joint Computer Conference (AFIPS) 21, pp. 335–44 (1962) — description of CTSS
• F. J. Corbató and V. A. Vyssotsky, "Introduction and Overview of the MULTICS System", Proc. Fall Joint Computer Conference (AFIPS) 27, pp. 185–96 (1965)
• P. J. Denning, "Virtual Memory", Computing Surveys Vol. 2, pp. 153–89 (1970)
• J. B. Dennis, "Segmentation and the Design of Multi-Programmed Computer Systems," JACM Vol. 12, pp. 589–602 (1965)
  ― virtual memory requirements for Project MAC, destined for GE 645
• C. A. R. Hoare and R. H. Perrott, Eds., Operating Systems Techniques, Academic Press, Inc., New York (1972)
• T. Kilburn, D. B. G. Edwards, M. J. Lanigan, and F. H. Sumner, "One-Level Storage System", IRE Trans. Electron. Computers EC-11, pp. 223–35 (1962)
  ― Manchester/Ferranti Atlas
• R. A. Nelson, "Mapping Devices and the M44 Data Processing System," Research Report RC 1303, IBM Thomas J. Watson Research Center (1964)
  ― about the IBM M44/44X
• R. P. Parmelee, T. I. Peterson, C. C. Tillman, and D. J. Hatfield, "Virtual Storage and Virtual Machine Concepts", IBM Systems Journal, Vol. 11, pp. 99–130 (1972)

Additional on-line CP/CMS resources

• febcm.club.fr — Information Technology Timeline, 1964–74
• www.multicians.org — Tom Van Vleck's short essay The IBM 360/67 and CP/CMS
• www.cap-lore.com — Norman Hardy's Short history of IBM's virtual machines
• www.cap-lore.com — Norman Hardy's short description of the "Blaauw Box"

Other resources

• IBM Redbooks Publication – z/VM textbook
• IBM: z/VM portal
• IBM: z/VM manuals
• VM/PC documentation on bitsavers

CP/CMS family relationships
→ derivation     >> strong influence     > some influence/precedence
CTSS
	> IBM M44/44X
	>> CP-40/CMS → CP[-67]/CMS	→ VM/370 → VM/SE versions → VM/SP versions → VM/XA versions → VM/ESA → z/VM
		→ VP/CSS
	> TSS/360
	> TSO for MVT → for OS/VS2 → for MVS → ... → for z/OS
	>> MULTICS and most other time-sharing platforms