Path: utzoo!attcan!uunet!wucs1!wucs2!jps
From: jps@wucs2.UUCP (James Sterbenz)
Newsgroups: comp.arch
Subject: Re: stack machines (Burroughs)
Keywords: RISC, real-time
Message-ID: <853@wucs2.UUCP>
Date: 13 Jun 88 21:04:07 GMT
References: <1521@pt.cs.cmu.edu> <1532@pt.cs.cmu.edu> <476@pcrat.UUCP> <2868@louie.udel.EDU> <370@dlscg1.UUCP> <3147@polyslo.UUCP> <3693@saturn.ucsc.edu>
Reply-To: jps@wucs2.UUCP (James Sterbenz)
Organization: Washington U. in St. Louis
Lines: 28

In article <3693@saturn.ucsc.edu> haynes@ucscc.UCSC.EDU (Jim Haynes) writes:
>Well there are different meanings to "sophisticated", but for real
>sophistry you need to see a system that uses a lot of letter
>abbreviations like JES and MVS and VS1 and VM and CMS and OS and ...
>where each flavor needs a different compiler and file system.

I personally find the 5000/6000/7000/A architectural basis very elegant,
but c'mon, get your history right ... 
these are not comparable...

OS/MFT -> OS/MVT -> OS/VS (later VS1) -> VS2 (SVS) -> MVS -> MVS/XA
even though some of these have been available concurrently
(MFT and MVT,  VS1 and MVS) for periods of time, it is essentially
a sucession of version of the SAME system -- of the above list,
the ONLY currently available versions are MVS(/SP) and MVS/XA.

It would have been like having 5500 MCP, 6500 MCP, MCP MARK whatever ...
for a similar list.  If you read an MCP manual or system architecture manual
you'll find PLENTY of obnoxious acronyms (e.g. MSCW).

By the way ...

JES (Job Entry Subsystem) is a part of MVS (optional in the OS days,
but now required: JES2 from HASP, JES3 from ASP).

VM is a completely different operating system consisting of
VM, the hypervisor (CP-44 -> CP-67 -> CP) and various
guest operating systems, of which CMS is one.   MVS can run under CP.