Edward:

I can say something about that, as I was a member of the team that developed the prototype and was scheduled to become the leader of one of the two development teams charged with the planned "CMS on MVS" product. While we were getting staffed up, IBM canceled the project. The planned team leader for the other development team, who was also a member of the prototype team, was the late Karl Finkemeyer, who had created a PR/SM prototype he called "The Thin Layer" while working at the Heidelberg Scientific Center.

We had successfully IPLed and run CMS in a TSO address space using SIE. The CMS nucleus was unmodified. Our prototype was proof of the feasibility of the product. There was no VM in our prototype, though we had to implement some underlying functionality. My part in the prototype was the implementation of the CMS file system, which I did using Control Interval access in a VSAM data set. I believe that the idea was later used as a basis for PDS/E and HFS, although by the time both of these came along, I had left IBM and gone into consulting

Mike Myers
Mentor Services Corporation

 On 02/10/2017 08:53 PM, Edward Finnell wrote:
Back in the days. There was CMS for MVS in the early 80's. One of the
developers was a regular at SHARE and I guess resigned due to the decision to
shelve it for 'Marketing Considerations'. Went on the shelf right next to the
  Clist Compiler-CLIC.
In a message dated 2/10/2017 6:58:25 P.M. Central Standard Time,
charl...@mcn.org writes:

Would  not the proper phrase be "run independently of CP"? CMS is a
component
of  z/VM; it can't be independent of z/VM, it *is*  z/VM.


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to