The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.
Anne & Lynn Wheeler <[EMAIL PROTECTED]> writes:
> There was a version of CP67 that was converted to run on 370s ("CP67-I"
> system) ... which was used extensively inside IBM pending availability
> of VM370 product. In the morph of CP67 to VM370 product, the CCWTRANS
> channel program translation routine became DMKCCW.
re:
http://www.garlic.com/~lynn/2008i.html#68 EXCP access methos
an early use of the internal network was distributed development
project between the science center and endicott.
the internal network technology was created at the science center
(as well as cp67, gml, lots of other stuff)
http://www.garlic.com/~lynn/subtopic.html#545tech
the internal network was larger than the arpanet/internet from just
about the beinning to possibly mid-85
http://www.garlic.com/~lynn/subtopic.html#internalnet
the 370 virtual memory hardware architecture was well specified ... and
endicott approached the science center about providing 370 virtual
machine support for early software testing ... i.e. in addition to
providing 360 and 360/67 virtual memory emulation ... cp67 would be
modified to also provide option for 370 and 370 virtual memory
emulation.
the original cms multi-level source maintenance system was developed as
part of this effort (cms & cp67 had source maintenance but was single
level "update").
part of the issue was that this would run on the science center cp67
time-sharing system which including access by numerous non-employees
(many from various educational institutions in the cambridge/boston
area). 370 virtual memory was a closely held corporate secret and so
there had to be a lot of (security) measures to prevent it being
divulged.
the basic cambridge cp67 time-sharing system ran "CP67-L".
eventually, in a 360/67 virtual machine, a "CP67-H" kernel ran which had
the modifications to provide 370 virtual machines as an option. This
provided isolation, preventing the general time-sharing users from being
exposed to any of the 370 features.
then a set of updates were created that modified the CP67 kernel to run
on 370 "hardware" .... a "CP67-I" kernel would then run in a 370 virtual
machine provided by a "CP67-H" kernel running in a 360/67 virtual
machine.
CP67-I was in regular operation a year before the first engineeing 370
machine with virtual memory hardware was working. In fact, CP67-I was
used as a test case when that first engineering machine became
operational.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
