Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!amdahl!esf00 From: esf00@amdahl.amdahl.com (Elliott S. Frank) Newsgroups: comp.arch Subject: Historical correction (was Re: Horizontal pipelining) Message-ID: <18624@amdahl.amdahl.com> Date: Mon, 23-Nov-87 12:15:21 EST Article-I.D.: amdahl.18624 Posted: Mon Nov 23 12:15:21 1987 Date-Received: Thu, 26-Nov-87 02:35:27 EST References: <201@PT.CS.CMU.EDU> <388@sdcjove.CAM.UNISYS.COM> <988@edge.UUCP> <393@sdcjove.CAM.UNISYS.COM> <3801@ptsfa.UUCP> Reply-To: esf00@amdahl.amdahl.com (Elliott S. Frank) Organization: The Beige Building Full of Bright Engineers, Inc. Lines: 39 Keywords: multiple users In article <3801@ptsfa.UUCP> dmt@ptsfa.UUCP (Dave Turner) writes: >>In article <988@edge.UUCP> doug@edge.UUCP (Doug Pardee) writes: >>>OS/MFT became (was the basis for) OS/VS1. OS/MVT was the basis for OS/VS2. >>>Release 2 of OS/VS2 was the first MVS. Inevitably, OS/VS2 Release 1 became >>>known to history as SVS. > >I thought that OS/VS1 was called SVS. > Some taxonomy: OS/PCP (Primary Control Program == real memory single task OS/360) --> evolutionary dead end OS/MFT (Multiprogramming with a Fixed number of Tasks == real memory operating system assigning a memory partition for each "job step" task) --> OS/VS/1 [24-bit fixed partition operating system] --> evolutionary dead end OS/MVT (Multiprogramming with a Variable number of Tasks == real memory operating system assigning necessary memory for each "job step" task) --> OS/VS/2 [24-bit dynamic partitioned operating system] OS/VS/2 Release 1 == SVS (Single Virtual System == 24-bit virtual address space dynamically partitioned among active "job step" tasks) OS/VS/2 Release 2 == MVS (Multiple Virtual Spaces == created 24-bit address space for each "job step" task) And what is a "job step" task? Ah, ... :-) -- Elliott Frank ...!{hplabs,ames,sun}!amdahl!esf00 (408) 746-6384 or ....!{bnrmtv,drivax,hoptoad}!amdahl!esf00 [the above opinions are strictly mine, if anyone's.] [the above signature may or may not be repeated, depending upon some inscrutable property of the mailer-of-the-week.]