It’s been a very long time in the mists of my memory that someone mentioned cp/67 cms. I think it ran on a 360/40 at New York Psychic Center. Sent from my iPhone
> On Jun 20, 2026, at 07:37, Jay Maynard > <[email protected]> wrote: > > CP/67 won't run on a 370. The virtual memory implementation is different > enough to keep it from running. I don't know if CP/67's CMS will run on a > bare 370, though it will run under VM/370, so maybe... > > If it'll run on a bare 370, it should run on a P/370. > >> On Fri, Jun 19, 2026 at 10:14 PM Farley, Peter < >> [email protected]> wrote: >> >> Just out of pure curiosity, I wonder if there are any surviving copies of >> that “bare metal” CMS system and its documentation outside of IBM deep >> archives (i.e., gathering dust at Iron Mountain). >> >> It would be interesting to bring it up under S/370 emulation or on a >> surviving P370 system if anyone has one that’s still operational, just to >> see it work, but probably also somewhat frustrating without the supporting >> documentation. >> >> Peter >> >> From: IBM Mainframe Discussion List <[email protected]> On Behalf >> Of Mark S Waterbury >> Sent: Friday, June 19, 2026 10:39 PM >> To: [email protected] >> Subject: Re: GC20-1757 - IBM Virtual Machine Facility/370 Features >> Supplement >> >> >> The original "CMS" (Cambridge Monitor System) of CP-67 could run on a >> "bare" machine, and this was used to do the initial "SYSGEN" of CP-67, e.g. >> to specify the I/O configuration etc. to install CP-67 on an IBM S/360 >> model 67. >> >> >> >> By the time VM/370 became available in late 1972 or early 1973, the VM >> version of "CMS" (Conversational Monitor System) could no longer run on any >> "bare" machine as it relied on a number of CP services provided via the >> DIAGnose instruction (aka. the "hypervisor call" in today's lingo.) >> >> -- >> >> >> >> This message and any attachments are intended only for the use of the >> addressee and may contain information that is privileged and confidential. >> If the reader of the message is not the intended recipient or an authorized >> representative of the intended recipient, you are hereby notified that any >> dissemination of this communication is strictly prohibited. If you have >> received this communication in error, please notify us immediately by >> e-mail and delete the message and any attachments from your system. >> >> >> ---------------------------------------------------------------------- >> For IBM-MAIN subscribe / signoff / archive access instructions, >> send email to [email protected] with the message: INFO IBM-MAIN >> > > > -- > Jay Maynard > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
