🚀 go-pugleaf

Anne & Lynn Wheeler <ly...@garlic.com> writes:
> other drift, early 70s, my wife worked for BBN on gov. contracts;
> SIGMA5/SIGMA7 lashup, PLI cross-compiler for Litton computers. They then
> asked her to go to Cambridge to inteview for the IMP/ARPANET group, but
> she didn't want to leave DC area. She eventually left and joined IBM
> gburg in 1973 on Future System project, working for Les Comeau (who had
> been involved in the original virtual machine implementations at the
> cambridge science center).

re:
http://www.garlic.com/~lynn/2018d.html#108 Frank Heart Dies at 89

more trivia: when FS blew up ... past posts
http://www.garlic.com/~lynn/submain.html#futuresys

my wife co-authored AWP39 (architecture white paper) "peer-to-peer
networking" with Bert Moldow. They had to qualify it with "peer-to-peer"
because the communication group had co-oped "networking" for SNA (we
joke that it wasn't a system, it wasn't a network and it wasn't an
architecture, it was terminal control infrastrcuture).

she was also one of the "ASP" catchers in the IBM gburg group for
turning into JES3 and co-author of "JESUS" (JES unified systems) ... all
the features of JES2 & JES3 that the respective customers could live w/o
... for various reasons never came to fruition. all sorts of past
HASP, JES, NJI/NJE, etc posts
http://www.garlic.com/~lynn/submain.html#hasp

she then gets con'ed into going to POK to be in charge of
loosely-coupled (mainframe for cluster) architecture where she did
"peer-coupled shared data" architecture. She didn't remain very long, in
part because 1) constant battles with communication group trying to
force her to use SNA for loosely-coupled operation and 2) little uptake
... except for IMS hot-standby, until SYSPLEX and Parallel SYSPLEX.

IMS
https://en.wikipedia.org/wiki/IBM_Information_Management_System
recent availability
https://www.ibm.com/developerworks/community/blogs/RohitShetty/entry/high_availability_cold_warm_hot?lang=en
parallel sysplex
https://en.wikipedia.org/wiki/IBM_Parallel_Sysplex

mid-80s, IMS hot-standby could be up and operational almost immediately
... but it had communication group problem. The stand-by VTAM then had
to recreate all the terminal sessions ... establishing sessions in VTAM
was enormously heavy-weight process ... and for large operations (say a
few tens of thousands of ATM machines) it could take over 90mins.

I was roped into working with a baby bell that had built a NCP/VTAM
emulator on series/1 with a whole bunch of additional features. It ran
real networking between series/1s ... but emulated 37x5/NCP to host VTAM
and spoofed cross-domain ownership of resources (terminals).  Among
other things, it could fake shadow sessions to stand-by machine
... which would make "real" IMS hot-standby almost immediate.

We were working on turning it out as an IBM "TYPE-1" product on Series/1
with follow-on plans to port it to the (unannounced) RS/6000. We had
done everything we thought possible to brickwall off attempts by the
communication group to kill the effort ... what the communication group
did next to kill it can only be described as truth is stanger than
fiction.

a couple old posts about Series1 NCP/VTAM (PU4/PU5)
http://www.garlic.com/~lynn/99.html#67 System/1 ?
http://www.garlic.com/~lynn/99.html#70 Series/1 as NCP (was: Re: System/1 ?)

peer-coupled shared data posts
http://www.garlic.com/~lynn/submain.html#shareddata

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