[email protected] (Lindy Mayfield) writes:
> i can do that on vm?  create my own instruction?

originally virtual machine system was cp40 done on a 360/40 with custom
hardware modifications to support virtual memory.

when standard virtual memory became available with 360/67 ... cp40
morphed into cp67.

370 was originally announced pretty much the same as 360 ... with a few
new instructions, but w/o virtual memory.

there was a special project jointly between the science center and
endicott to modify cp67, implementing 370 virtual machines (supporting
the full set of unannounced 370 virtual memory features ... various bits
and fields differed from 360 virtual memory architecture).

there was also a set of modifications to cp67 that would run with 370
virtual memory hardware (instead of 360/67 virtual memory). that was up
and running in 370 virtual machine (on cp67 running on real 360/67) a
year before the first engineering 370 with virtual memory hardware was
operational (a 370/145 in endicott).

there was a security issue at the science center since they had some
number of non-employee users of the cp67 system from various educational
institutions in the boston area. so to help avoid unannounced 370
virtual memory from leaking the standard operation was:

real 360/67 hardware
  "cp67l" system w/o 370 modifications
    "cp67h" system running in 360/67 virtual machine providing 
    370 virtual machines
      "cp67i" system running in a 370 virtual machine providing
      370 virtual machines
         "cms" running in 370 virtual machine

non-employees using the "cp67l" system wouldn't have visability into
what the "cp67h" system was doing in a separate virtual machine (or that
there was 370 virtual machines or "cp67i" systems.

when engineering 370s with virtual memory support became available, they
were normally run with the "cp67i" system ... long before vm370 became
available. Internally, there was also "cp67sj" system ... which was a
"cp65i" system with modifications done by San Jose with device support
for 3330 disks and 2305 fixed head paging devices.

After the 23jun69 "unbundling" announcement ... starting to charge for
application software, SE services, and other stuff ... there was issue
with training for new SEs. misc. past posts mentioning unbundling
http://www.garlic.com/~lynn/submain.html#unbundle

New SEs had previosly gotten a lot of experience ... essentially in an
apprentice position as part of large SE team at customer sites. With
starting to charge for SE serices ... nobody could figure out how to do
the "apprentice" thing. As a result, several internal CP67 virtual
machine datacenters were set up as part of "HONE" ... supposedly to give
SEs in branch offices, remote/online "hands-on" experience running
various operating systems in cp67 virtual machines.

After the initial 370 announcement, a subset of the "cp67h" changes were
applied to the HONE systems ... to allow (non-virtual memory) 370
virtual machines (supporting the new instructions in the original 370
announcement). This would allow SEs to build & test operating systems
for "370" operation. misc. past posts mentioning HONE:
http://www.garlic.com/~lynn/subtopic.html#hone

the science center had also ported apl\360 to cms for cms\apl. some
number of sales & marketing support applications started to be
implemented (in apl) and also deployed on HONE. eventually the sales &
marketing (apl) applications became so extensive that they eventually
completely crowded out the SE virtual operating system activity. At some
point, branch office sales had to process customer orders thru various
HONE applications before they could be submitted (and HONE datacenters
started to pop up around the world). One of my hobbies was supporting
HONE operation ... and as a new employee fresh out of college ... I got
some number of overseas trips as part of the HONE proliferation.

I had maintained large amount of cp67 & cms source (replicated on
multiple tapes) up through the mid-80s.  however, at one point there was
an operational problem at the Almaden datacenter where random tapes were
selected for mounting as scratch ... and all tapes were overwritten.
Old email pulling bits & pieces from the tapes for Melinda Varien (not
long before they were lost):
http://www.garlic.com/~lynn/2006w.html#email850906
http://www.garlic.com/~lynn/2006w.html#email850908
http://www.garlic.com/~lynn/2006w.html#email850908b
in these old posts
http://www.garlic.com/~lynn/2006w.html#42
http://www.garlic.com/~lynn/2006w.html#48

Melinda's webpage:
http://www.princeton.edu/~melinda/

-- 
40+yrs virtualization experience (since Jan68), online at home since Mar1970

----------------------------------------------------------------------
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

Reply via email to