MVT
MVT is an acronym for Multiprogramming with a Variable number of Tasks. It was intended as the operating system for the larger machines in the System/360 family, introduced in 1964, but MVT did not become available until 1967. Early versions had many problems and the simpler MFT continued in use for many years. It is a very old forerunner of IBM's MVS and z/OS.
Long since dead and buried, it is of historical interest as the most advanced of the early OS/360 operating systems and the one most influential in later developments.
In particular, the I/O queueing of all the OS/360 family left a lot to be desired. This was addressed by two field-developed packages: HASP, the Houston Automated Spooling Package, and ASP. ASP stood for Attached Support Processor. Originally, that was something like a 360/40 controlling a 360/65 or greater processor through a magnetic tape channel controller processor. We had this nightmare at the university I attended in the late 1960's but we junked it for HASP which ran on the 360/65 alone (really a 67 with the TSO hardware turned off) with first OS 360/MFT and later MVS (when it worked). God bless HASP, written by 5 people who knew what they were doing. ASP was a total lost at the time, designed to sell second computers, mainly 360/40s. HASP needed only one computer and MTF to start with. Later, with MVS, it was the standard. That was for a couple of years.
HASP was developed by IBM Federal Systems Division contractors at the Johnson Space Center in Houston. In MVS, HASP became JES2, the Job Entry Subsystem. It was many years before the HASP labels were removed from the JES2 source, and the messages issued by JES2 are still prefixed with $HASP.
ASP was developed to provide efficient use of multiple OS/360 systems working in conjunction, and allowed one central system to distribute jobs to multiple connected systems. ASP became JES3.
See Also: OS/360