The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.


shmuel+ibm-m...@patriot.net (Shmuel Metz  , Seymour J.) writes:
> You don't consider SEPP (VM/SE) or BSEPP (VM/BSE) to be VM releases?

re:
http://www.garlic.com/~lynn/2010d.html#43 What was old is now new again (water 
chilled)

they were charged for kernel add-ons to the free vm370 release 6 base.

as part of 23jun69 unbundling announcement, there was start of charging
for application software (somewhat as the result of various litigation),
however they managed to make the case that kernel software was still
free.
http://www.garlic.com/~lynn/submain.html#unbundle

also discussed in this recent posts:
http://www.garlic.com/~lynn/2010d.html#42 search engine history, was Happy 
DEC-10 Day
http://www.garlic.com/~lynn/2010e.html#24 Unbundling & HONE

with the demise of future system project ... there was mad rush to get
items back into the 370 product pipeline ... also there have been claims
that it was the distraction of the FS product (and lack of products)
that allowed clone processors to get foothold in the marketplace. misc.
past FS posts
http://www.garlic.com/~lynn/submain.html#futuresys

part of the rush to get things back into 370 product pipeline
contributed to picking up various 370 things that I had been doing
during the FS period for product release. some recent discussion
(as well as "Unbundling & HONE" post referenced above)
http://www.garlic.com/~lynn/2010e.html#21 paged-access method

One of the things was the resource manager. However, possibly because of
the foothold that the clone processors were getting in the market, there
was decision to start charging for kernel software ... and my resource
manager was selected as guinea pig. Also discussed here
http://www.garlic.com/~lynn/2010e.html#25 HONE Compute Intensive

which shipped in the middle of the vm370 release 3 time-frame.  As
mentioned in the above ... vm370 multiprocessor support was to go out in
vm370 release 4 ... but design/implementation was dependent on lots of
code in the resource manager. The initial policy for kernel charging was
that hardware support would still be free (including multiprocessor
support) and couldn't have prerequisite that was charged for ...  as in
my resource manager. The eventually solution was to move approx. 90% of
the code from the resource manager into the "free" base ... but leave
the price of the "release 4" resource manager the same (as release 3,
even tho it was only about 10% of the code).

for vm370 release 5, the resource manager was repackaged with some
amount of other code ... including "multiple shadow table support"
... discussed here:
http://www.garlic.com/~lynn/2010e.html#1 LPARs: More or Less?

and renamed HPO (i.e. HPO was the charged for software that fit ontop of
vm370 release 5).

for vm370 release 6, the charged for software was repackaged, a full set
of all the software (previously HPO) which was renamed SEPP ... and a
subset of the SEPP software ... at a lower price that was named BSEPP.

So neither SEPP nor BSEPP were free ... they were both kernel add-on
software for the free vm370 release 6 base, that was charged for.

When it came time for vm370 release 7, there was transition to charging
for all kernel software ... and everything was merged back into single
charged for kernel renamed VM/SP (and there was no more "vm370"
releases).

vm370 release 6 being free has been made available for Hercules (370
virtual machine on intel platform) ... but not any of the charged for
software ... my resource manager, HPO, SEPP, BSEPP, vm/sp, etc.

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

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to