Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.folklore.computers > #222904

Re: Fred P. Brooks, 1931-2022

Show all headers | View raw

Quadibloc <jsavard@ecn.ab.ca> writes:
> Which full architecture document no doubt was highly secret within IBM.
>
> However, nowadays, stuff like Program Logic Manuals, which were IBM
> Confidential, are turning up on Bitsavers.

PLMs were less so, it was the unannounced features ... like before 370
virtual memory ... somebody leaked some details to industry press which
resulted in witch hunt ... and then all internal IBM copiers were
retrofitted with serial under the glass that would appear on every page
copied ... to try and help localize where leak might have originated.

Cambridge did have a joint project with Endicott to modify CP67 to
provide 370 (virtual memory architecture) virtual machines. This was in
regular operation a year before any engineering 370 hardware supporting
virtual memory was operational. Cambridge had to demonsrate fairly
strong security since staff, professors, and students from Boston area
univ. were also using the Cambridge CP67 system.

Then for FS
http://www.jfsowa.com/computer/memo125.htm
http://people.cs.clemson.edu/~mark/fs.html
https://www.ecole.org/en/session/49-the-rise-and-fall-of-ibm
https://en.wikipedia.org/wiki/IBM_Future_Systems_project

IBM tried to eliminate all classified hard copy documents, specially
modified VM370 system where documents could only be read on specifically
identified 3270 terminals and all functions but reading was disabled.

When FS imploded, there was mad rush to get stuff back into 370 product
pipelines ... including kicking off 370/xa and quick and dirty 3033 and
3081 in parallel. Initially 370/xa hard copy were "IBM registered
confidential" (referred to as "811" for nov78 publication date) ... each
page had off-color, page size, document serial number embossed ... serial
number was registered to specific person and there were periodic
surprise security audits to make sure they were kept under double
lock&key.

IBM security classification had evovled to:

IBM Internal Use Only
IBM Confidential
IBM Confidential - Restricted
IBM Confidential - Registered

something of a joke: 1974, CERN had done an analysis comparing VM370/CMS
and MVS/TSO and presented result at (IBM mainframe user group) SHARE
... and copies were freely available ... except inside IBM where they
got stamped "IBM Confidential - Restricted" (available on need to know
basis only) ... wanted as much as possible to minimize availability of
the analysis to IBM employees.

I ran into something similar when TYMSHARE
https://en.wikipedia.org/wiki/Tymshare
in Aug1976 started offering their CMS-based online computer
conferencing facility free to SHARE as VMSHARE ... archives
here:
http://vm.marist.edu/~vmshare

I cut a deal with TYMSHARE to get monthly tape dump of all VMSHARE files
for putting up on internal network and internal systems. The biggest
problem I had were the lawyers concerned that IBM employees would be
contaminated exposed to customer information (and/or internal employees
were being fed stuff about customers that didn't correspond to what
customers were actually saying).

-- 
virtualization experience starting Jan1968, online at home since Mar1970

Back to alt.folklore.computers | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

Fred P. Brooks, 1931-2022 Quadibloc <jsavard@ecn.ab.ca> - 2022-11-29 12:11 -0800
  Re: Fred P. Brooks, 1931-2022 Peter Flass <peter_flass@yahoo.com> - 2022-11-29 13:21 -0700
  Re: Fred P. Brooks, 1931-2022 D.J. <chucktheouch@gmnol.com> - 2022-11-29 14:49 -0600
    Re: Fred P. Brooks, 1931-2022 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2022-11-29 23:24 +0000
      Re: Fred P. Brooks, 1931-2022 Mike Spencer <mds@bogus.nodomain.nowhere> - 2022-11-30 03:11 -0400
        Re: Fred P. Brooks, 1931-2022 Ahem A Rivet's Shot <steveo@eircom.net> - 2022-11-30 08:56 +0000
          Re: Fred P. Brooks, 1931-2022 Mike Spencer <mds@bogus.nodomain.nowhere> - 2022-11-30 14:27 -0400
        Re: Fred P. Brooks, 1931-2022 "Kurt Weiske" <kurt.weiske@realitycheckbbs.org.remove-kbd-this> - 2022-11-30 09:26 -0800
  Re: Fred P. Brooks, 1931-2022 Anne & Lynn Wheeler <lynn@garlic.com> - 2022-11-29 18:31 -1000
    Re: Fred P. Brooks, 1931-2022 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2022-11-30 17:57 +0000
      Re: Fred P. Brooks, 1931-2022 Peter Flass <peter_flass@yahoo.com> - 2022-11-30 15:57 -0700
        Re: Fred P. Brooks, 1931-2022 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-30 23:10 +0000
          Re: Fred P. Brooks, 1931-2022 Peter Flass <peter_flass@yahoo.com> - 2022-11-30 18:19 -0700
            Re: Fred P. Brooks, 1931-2022 Peter Flass <peter_flass@yahoo.com> - 2022-11-30 18:24 -0700
          Re: Fred P. Brooks, 1931-2022 Anne & Lynn Wheeler <lynn@garlic.com> - 2022-11-30 16:39 -1000
            Re: Fred P. Brooks, 1931-2022 Quadibloc <jsavard@ecn.ab.ca> - 2022-12-01 16:03 -0800
              Re: Fred P. Brooks, 1931-2022 Anne & Lynn Wheeler <lynn@garlic.com> - 2022-12-01 14:44 -1000
        Re: Fred P. Brooks, 1931-2022 Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2022-12-01 05:19 +0000
        Re: Fred P. Brooks, 1931-2022 scott@slp53.sl.home (Scott Lurndal) - 2022-12-01 15:19 +0000
          Re: Fred P. Brooks, 1931-2022 Bob Eager <news0009@eager.cx> - 2022-12-01 21:55 +0000
            Re: Fred P. Brooks, 1931-2022 Quadibloc <jsavard@ecn.ab.ca> - 2022-12-01 15:59 -0800
        Re: Fred P. Brooks, 1931-2022 Robin Vowels <robin.vowels@gmail.com> - 2022-12-01 18:07 -0800
      Re: Fred P. Brooks, 1931-2022 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-30 23:10 +0000

csiph-web