This article relies largely or entirely on a single source .(August 2018) |
![]() VPS login screen | |
Developer | McGill University, Boston University |
---|---|
Working state | Historic |
Marketing target | IBM mainframe computers |
Available in | English |
Platforms | IBM System/370 – IBM 3090 |
License | Proprietary |
VPS/VM (Virtual Processing System/Virtual Machine) was an operating system that ran on IBM System/370 – IBM 3090 computers at Boston University in general use from 1977 to around 1990, and in limited use until at least 1993. During the 1980s, VPS/VM was the main operating system of Boston University and often ran up to 250 users at a time when rival VM/CMS computing systems could only run 120 or so users.
Each user ran in a Virtual Machine under VM, an IBM hypervisor operating system. VM provided the virtual IBM 370 machine which the VPS operating system ran under. The VM code was modified to allow all the VPS virtual machines to share pages of storage with read and write access. VPS utilized a shared nucleus, as well as pages used to facilitate passing data from one VPS virtual machine to another. This organization is very similar to that of MVS; substituting Address Spaces for Virtual Machines.
According to Craig Estey, who worked at the Boston University Academic Computing Center between 1974 and 1977: [1]
VPS's original name was RACS (remote access computing system), originally developed at McGill University in Montreal from 1966 onward. The name got shortened to RAX. It was up and running from [at least] 1973 at BU [probably earlier]. Although there was a period of joint development, by 1972, McGill and BU started to diverge and McGill rebranded their version of RAX as MUSIC/SP at that time. MUSIC/SP has its own wiki entry with a few more details, a fair amount is applicable to BU/RAX...
VPS development was evolutionary, rather than revolutionary. The changes necessary were phased in over time while the system was called RAX. It was rebranded VPS, mostly because the resulting system was good enough that there was an effort afoot to monetize it commercially...
MUSIC/SP remained a standalone OS. But, BU had an IBM 370/145 and they ran IBM's VM/370 virtual machine hypervisor and RAX became a client OS. Originally, it used only one VM for all users. But, RAX became more and more "hypervisor aware". Eventually, it gave each RAX user their own VM (under the parent OS VM/370, but invisible to the RAX user), so eventually, RAX control resembled a multicore/distributed architecture of many [virtual] machines, with a single shared memory copy of the RAX client. When that work was completed, that's when it was renamed VPS.
An IBM-based operating system, and quite like some DOS/VSE time sharing options, VPS/VM provided the user an IBM 3270 full screen terminal (a green screen) and a user interface that was like VM/CMS. Each user had an 11 megabyte virtual machine (with a strange 3 megabyte memory gap in the middle) and, from 1984 onwards, could run several programs at a time.
The operating system was sparsely documented but was written first by Charles Brown, a BU doctoral student, and John H. Porter, a physics PHD, who later became the head of the VPS project (and eventually Boston University's vice president for information systems and technology [2] ). Marian Moore wrote much of the later VM code necessary to run the VPS system. Josie Bondoc wrote some of the later VPS additions, like UNIX piping.
Many MVS/VM programs ran on VPS/VM, such as XEDIT, and compilers for Pascal, PL/1, C and Cobol. These MVS/VM programs ran under an OS simulation program that simulated the OS/VM supervisor calls (SVCs). Margorie Orr supervised the OS simulation program development and maintenance. Some of the programmers who wrote parts of the OS simulation package, or maintained it were Margorie Orr, Timothy Greiser, Daniel Levbre, John Coldwell Lotz, and Paul Cheffers.
Michael Krugman wrote some of the early main utilities such as IFMSG, the JCL language for VPS, and also MAIL, the early email program. SENDMAIL, written by Francis Costanzo, implemented email, under the BITNET system.
Some pre SQL databases installed on VPS were FOCUS and NOMAD2.
Michael Gettes wrote an early and quick HELP system.
The file system was not hierarchical and originally each file had to have a unique 8 character filename. This eventually grew onerous and each user was given their own private directory.
Tapes and IBM disk files were supported as well as native VPS text files.
There was a very simple shell and no patterns were supported except for the PAW computer program, written by Paul Cheffers.
The graphics department, under Glenn Bresnahan, essentially, ported over most of the UNIX utilities in the mid 1980s.
William Marshall did much of the early system documentation, as well as providing PL/1 support. Joe Dempty was the User Services director. Diana Robanske was a statistics consultant and ran student assistance services from 1980-1985. John Houlihan was also a User Services statistics consultant.
VPS/VM was a working pre-GUI IBM operating system, and could often run more users than other IBM TSO-based systems. When most University-based systems only provided editors and compilers, VPS provided these services to a 10,000 BU university community for over 10 years.
VPS/VM policy was for the operating system and main utilities to be written in IBM 370 assembler language. This decision restricted the development of the system and it ultimately could not compete with the UNIX-based systems which eventually replaced it. However, VPS eventually modeled many of the features of then-current operating systems around the world and was a keen trainer for many companies that needed IBM370 assembler programmers in the 1980s.
AIX is a series of proprietary Unix operating systems developed and sold by IBM for several of its computer platforms.
IBM mainframes are large computer systems produced by IBM since 1952. During the 1960s and 1970s, IBM dominated the computer market with the 7000 series and the later System/360, followed by the System/370. Current mainframe computers in IBM's line of business computers are developments of the basic design of the System/360.
Multiple Virtual Storage, more commonly called MVS, is the most commonly used operating system on the System/370, System/390 and IBM Z IBM mainframe computers. IBM developed MVS, along with OS/VS1 and SVS, as a successor to OS/360. It is unrelated to IBM's other mainframe operating system lines, e.g., VSE, VM, TPF.
Computer operating systems (OSes) provide a set of functions needed and used by most application programs on a computer, and the links needed to control and synchronize computer hardware. On the first computers, with no operating system, every program needed the full hardware specification to run correctly and perform standard tasks, and its own drivers for peripheral devices like printers and punched paper card readers. The growing complexity of hardware and application programs eventually made operating systems a necessity for everyday use.
The Conversational Monitor System is a simple interactive single-user operating system. CMS was originally developed as part of IBM's CP/CMS operating system, which went into production use in 1967. CMS is part of IBM's VM family, which runs on IBM mainframe computers. VM was first announced in 1972, and is still in use today as z/VM.
MUSIC/SP was developed at McGill University in the 1970s from an early IBM time-sharing system called RAX.
This article presents a timeline of events in the history of computer operating systems from 1951 to the current day. For a narrative explaining the overall developments, see the History of operating systems.
VM 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.
CP/CMS is a discontinued time-sharing operating system of the late 1960s and early 1970s. It is known for its excellent performance and advanced features. Among its three versions, CP-40/CMS was an important 'one-off' research system that established the CP/CMS virtual machine architecture. It was followed by CP-67/CMS, a reimplementation of CP-40/CMS for the IBM System/360-67, and the primary focus of this article. Finally, CP-370/CMS was a reimplementation of CP-67/CMS for the System/370. While it was never released as such, it became the foundation of IBM's VM/370 operating system, announced in 1972.
A hypervisor, also known as a virtual machine monitor (VMM) or virtualizer, is a type of computer software, firmware or hardware that creates and runs virtual machines. A computer on which a hypervisor runs one or more virtual machines is called a host machine, and each virtual machine is called a guest machine. The hypervisor presents the guest operating systems with a virtual operating platform and manages the execution of the guest operating systems. Unlike an emulator, the guest executes most instructions on the native hardware. Multiple instances of a variety of operating systems may share the virtualized hardware resources: for example, Linux, Windows, and macOS instances can all run on a single physical x86 machine. This contrasts with operating-system–level virtualization, where all instances must share a single kernel, though the guest operating systems can differ in user space, such as different Linux distributions with the same kernel.
OfficeVision was an IBM proprietary office support application.
A logical partition (LPAR) is a subset of a computer's hardware resources, virtualized as a separate computer. In effect, a physical machine can be partitioned into multiple logical partitions, each hosting a separate instance of an operating system.
SCRIPT, any of a series of text markup languages starting with Script under Control Program-67/Cambridge Monitor System (CP-67/CMS) and Script/370 under Virtual Machine Facility/370 (VM/370) and the Time Sharing Option (TSO) of OS/VS2; the current version, SCRIPT/VS, is part of IBM's Document Composition Facility (DCF) for IBM z/VM and z/OS systems. SCRIPT was developed for CP-67/CMS by Stuart Madnick at MIT, succeeding CTSS RUNOFF.
VP/CSS was a time-sharing operating system developed by National CSS. It began life in 1968 as a copy of IBM's CP/CMS, which at the time was distributed to IBM customers at no charge, in source code form, without support, as part of the IBM Type-III Library. Through extensive in-house development, in what today would be termed a software fork, National CSS took VP/CSS in a different direction from CP/CMS. Although the two systems would eventually share many capabilities, their technical implementations diverged in substantive ways.
The IBM Time Sharing System TSS/360 is a discontinued early time-sharing operating system designed exclusively for a special model of the System/360 line of mainframes, the Model 67. Made available on a trial basis to a limited set of customers in 1967, it was never officially released as a supported product by IBM. TSS pioneered a number of novel features, some of which later appeared in more popular systems such as MVS. TSS was migrated to System/370 and 303x systems, but despite its many advances and novel capabilities, TSS failed to meet expectations and was eventually canceled. The Resident Supervisor of TSS/370 was used as the basis for a port of UNIX to the IBM mainframe. TSS/360 also inspired the development of the TSS/8 operating system.
In computing, virtualization is the use of a computer to simulate another computer. The following is a chronological list of virtualization technologies.
Operating System/Virtual Storage 1, or OS/VS1, is a discontinued IBM mainframe computer operating system designed to be run on IBM System/370 hardware. It was the successor to the Multiprogramming with a Fixed number of Tasks (MFT) option of System/360's operating system OS/360. OS/VS1, in comparison to its predecessor, supported virtual memory. OS/VS1 was generally available during the 1970s and 1980s, and it is no longer supported by IBM.
The history of IBM mainframe operating systems is significant within the history of mainframe operating systems, because of IBM's long-standing position as the world's largest hardware supplier of mainframe computers. IBM mainframes run operating systems supplied by IBM and by third parties.
A system virtual machine is a virtual machine (VM) that provides a complete system platform and supports the execution of a complete operating system (OS). These usually emulate an existing architecture, and are built with the purpose of either providing a platform to run programs where the real hardware is not available for use, or of having multiple instances of virtual machines leading to more efficient use of computing resources, both in terms of energy consumption and cost effectiveness, or both. A VM was originally defined by Popek and Goldberg as "an efficient, isolated duplicate of a real machine".