CP-67
CP-67 was the control program portion of CP/CMS, a virtual machine operating system developed for the IBM System/360-67 by IBM's Cambridge Scientific Center. 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. Details on the development and circumstances of CP-67 can be found in the article History of CP/CMS.
| Developer | IBM Cambridge Scientific Center (CSC) |
|---|---|
| OS family | CP/CMS |
| Working state | Historic |
| Marketing target | IBM mainframe computers |
| Available in | English |
| Platforms | IBM System/360-67 |
| Default user interface | Command-line interface |
| License | Proprietary |
| Preceded by | IBM CP-40 |
| Succeeded by | IBM CP-370 / VM/370 |
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 | |||
gollark: But it's bee.
gollark: The formatting thing isn't exactly in shells as much as the infrastructure surrounding them.
gollark: Shells contain some very bee things like:- in-band signalling of formatting- excessive stringyness, poor data structures- poor error handling- lack of advanced constructs- bad modularitybut cool things like:- easy to call out to other utilities- highly concurrency- file descriptor manipulation
gollark: I meant this ironically. Interactive Python is actually a terrible shell replacement.
gollark: REPLs are highly.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.