In one sense, we need to be careful about what we ask for. Do we want
z/OS to be easily available to those who want to find vulnerabilities
and crack the system? For security purposes are we better off with
some kind of regulated hobbyist access to z/OS running under z/VM at
data centers?
re:
http://www.garlic.com/~lynn/2010j.html#14 Multiprise 3k for personal Use?
http://www.garlic.com/~lynn/2010j.html#17 Personal use z/OS machines was Re: Multiprise 3k for personal Use?
http://www.garlic.com/~lynn/2010j.html#18 Personal use z/OS machines was Re: Multiprise 3k for personal Use?
http://www.garlic.com/~lynn/2010j.html#19 Personal use z/OS machines was Re: Multiprise 3k for personal Use?
aka, during the OCO-wars ... in the transition from freely available
source to object-code-only ... I don't remember being able to hide
threats and vulnerabilities being an argument ... it was about
protecting corporate property (i.e. source) in a competitive environment
with clone processors.
starting to charge for application software (23jun69 unbundling
announcement) was about various litigation ... but case had been made
that kernel/system software would still be free. later decision to start
charging for kernel software was in period when clone processors had
gained market foothold (during FS distraction, and my resource manager
was initial guinea pig for kernel software charging);
http://www.garlic.com/~lynn/submain.html#unbundle
OCO could be construed as further market inhibitors (in addition to
software no longer free).
sometimes (in OCO-wars) there were issues raised about protecting
customers from themselves ... that freely available source encourages
customer programmers to make modifications ... which would cause
problems/delays in moving to newer releases (things like newer source
was incompatible with older source). customer source modifications could
also result in delays in replacing existing machines with newer machines
(that might have various kinds of differences).
there was case where AT&T had gotten a highly modified versions of early
csc/vm system (w/o multiprocessor support) ... old csc/vm email
reference (long before OCO-wars, still when vm370 shipped with full
source maintenance):
http://www.garlic.com/~lynn/2006v.html#email731212
http://www.garlic.com/~lynn/2006w.html#email750430
AT&T then made a large number of their own source modifications (things
like virtual device support that ran over network connections ... aka
being able to run application at one AT&T facility ... thinking it was
doing i/o to local tape drive ... but tape drive was actually connected
to system at another AT&T facility) ... which was widely
distributed/used within AT&T.
Nearly a decade later, the national account manager for AT&T tracked me
down looking for help in moving AT&T off that csc/vm system to a more
current vm370. This was related to 3081 ... which was only going to be
available in multiprocessor configuration ... and there was not going to
be a non-multiprocessor (although this was later modified to ship 3083
... in large part because ACP/TPF didn't have multiprocessor
support). Since that particular csc/vm system (w/o multiprocessor
support) was so entrenched in AT&T ... they were going to be forced to
going to clone processor vendor that was selling newer uniprocessor
machines (early csc/vm systems didn't have multiprocessor support until
after the version that had escaped to AT&T; except for version that
escaped to AT&T ... my csc/vm systems were limited to large number of
internal installations ... which I could keep current).
misc. recent posts mentioning 3083
http://www.garlic.com/~lynn/2010.html#1 DEC-10 SOS Editor Intra-Line Editing
http://www.garlic.com/~lynn/2010.html#21 Happy DEC-10 Day
http://www.garlic.com/~lynn/2010d.html#14 Happy DEC-10 Day
http://www.garlic.com/~lynn/2010d.html#79 LPARs: More or Less?
http://www.garlic.com/~lynn/2010e.html#23 Item on TPF
http://www.garlic.com/~lynn/2010i.html#24 Program Work Method Question
http://www.garlic.com/~lynn/2010i.html#78 IBM to announce new MF's this year
other reference to 3081 (& future system)
http://www.jfsowa.com/computer/memo125.htm
--
42yrs virtualization experience (since Jan68), online at home since Mar1970