Jump to content

CP-67

From Wikipedia, the free encyclopedia
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Main article: CP/CMS
CP-67
DeveloperIBM Cambridge Scientific Center (CSC)
OS familyCP/CMS
Working stateHistoric
Marketing targetIBM mainframe computers
Available inEnglish
PlatformsIBM System/360-67
Default
user interface		Command-line interface
LicenseProprietary
Preceded byIBM CP-40
Succeeded byIBM CP-370 / VM/370

CP-67 is a hypervisor, or Virtual Machine Monitor, from IBM for its System/360 Model 67 computer.

CP-67 is the control program portion of CP/CMS, a virtual machine operating system developed by IBM's Cambridge Scientific Center in Cambridge, Massachusetts. It was a reimplementation of their earlier research system CP-40, which ran on a one-off customized S/360-40. CP-67 was later reimplemented (again) as CP-370, which IBM released as VM/370 in 1972, when virtual memory was added to the System/370 series.[1]

CP and CMS are usually grouped together as a unit, but the "components are independent of each other. CP-67 can be used on an appropriate configuration without CMS, and CMS can be run on a properly configured System/360 as a single-user system without CP-67."[2]

Minimum hardware configuration

The minimum configuation for CP-67 is:[3]: p.1 

Installation

Disks to be used by CP have to be formatted by a standalone utility called FORMAT, loaded from tape or punched cards. CP disks are formatted with fixed-length 829 byte records.

Following formatting, a second stand-alone utility, DIRECT, partitions the disk space between permanent (system and user files) and temporary (paging and spooling) space. DIRECT also creates the user directory identifying the virtual machines (users) available in the system. For each user the directory contains identifying information, id and password, and lists the resources (core, devices, etc) that this user can access, Although a user may be allowed access to physical devices it is more common to specify virtual devices, such as a spooled card reader, card punch, and printer. A user can be allocated one or more virtual disk units, "mini disks" [sic.], which resemble a real disk of the same device type, except that they occupy a subset of the space on the real device.[2]: p.37 

Family tree

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

See also

References

  1. ^ Randal, Allison (February 2020). "The Ideal Versus the Real: Revisiting the History of Virtual Machines and Containers". ACM Computing Surveys. 53 (1). arXiv:1904.12226. doi:10.1145/3365199. S2CID 139100890. Retrieved March 9, 2023.
  2. ^ a b IBM Corporation (October 1970). Control Program-67/Cambridge Monitor System (CP-67/CMS) Version 3 Program Number 360D-05.2.005 User's Guide (PDF). p. 1. Retrieved March 9, 2023.
  3. ^ IBM Corporation (May 1973). Control Program-67/Cambridge Monitor System (CP-67/CMS) Version 3.2 Program Number 360D-05.2.005 CP/67 Program Logic Manual (PDF). Retrieved March 9, 2023.
  4. ^ IBM Corporation (September 1968). IBM System/360 Model 65 Functional Characteristics (PDF). p. 5. Retrieved March 9, 2023.
Retrieved from "https://en.wikipedia.org/w/index.php?title=CP-67&oldid=1170135700"