[email protected] (Ted MacNEIL) writes: > colleges and universities. Looking at the short term. > > You are SO right! > > Shortly after I graduated from Waterloo, IBM stopped that programme; > shortly after that the University of Waterloo dropped COBOL as a > requirement for co-op students. > > Bingo! Bango! Bongo! The financial sector (Ontario & Toronto, at > least) went elsewhere for co-op, or stopped their programmes, > completely. > > Now, University of Waterloo computer graduates are PC weinies, > web-masters, and gamers. > > University of Waterloo's defence? > > "We are here to teach. Not to prepare future employees." > > BS! I went to Waterloo to become employable with the best credentials > available in the 1970's & 80's. > > Sorry for the topic drift, but I do think it all stemmed from IBM dropping > their generosity.
in the 60s, IBM gave enormous educational discounts ... all that appeared to have greatly curtailed with gov. litigation and the 23jun69 "unbundling" announcement (also started to charge for application software, SE services, other changes) ... some past posts http://www.garlic.com/~lynn/submain.html#unbundle then about the time various gov. sanctions expired in the early 80s, IBM "ACIS" was formed ... which was provided with significant amount of money for educational institutions. MIT Project Athena was jointly funded by DEC & IBM ... each providing $25M ... CMU got $50M ... I think ACIS initially got $300M for disbursement ... and when that was gone, they got more. I don't know of any ACIS money that was used for mainframes. As an example, CMU did unix "work-alike" MACH ... which was leveraged by Jobs at NeXT for its operating system, and became basis for MAC operating system replacement when Jobs returns to Apple. http://en.wikipedia.org/wiki/Mach_%28kernel%29 Kerberos was done in Project Athena. At the time, we periodically are asked to do periodic corporate visit to Project Athena to review their projects. I remember being there the week cross-domain protocol was being worked out http://en.wikipedia.org/wiki/Kerberos_%28protocol%29 A decade ago, a small Kerberos service company in Seattle area ... at the time, CEO was former head of IBM mainframe ... does a contract with Microsoft to integrate Kerberos into Windows as its authentication mechanism. We are working for a large financial services company and were periodically on-site at the company for various reasons. indirect reference in this article (although some is little garbled) http://www.ibmsystemsmag.com/mainframe/stoprun/Stop-Run/Making-History/ BITNET (where this ibm-main mailing list originated) & its sibling in Europe (EARN) was funded by IBM http://en.wikipedia.org/wiki/BITNET note above is slightly garbled with respect to NJE & RSCS. RSCS was originally done at the science center ... some past posts http://www.garlic.com/~lynn/subtopic.html#545tech some past posts about BITNET/EARN http://www.garlic.com/~lynn/subnetwork.html#bitnet RSCS/VNET was used for the internal network. JES2 with NJI/NJE had some nodes on the internal network (much of the code was from HASP that had source code identifier TUCC ... installation where it originated). The RSCS had layered design (which JES didn't) and RSCS could do drivers (like NJE) for other infrastructures. NJE used spare entries in the 255 psuedo-device table for network definitition ... (typically around 150 entries). Internal network was quickly greater than 255 nodes ... and NJE would trash traffic where it didn't have entry for either the origin or the destination. As a result JES2 systems were limited to boundary network nodes. Also NJE design was that traffic between JES2 systems at different release levels ... had tendancy to crash JES2 and their respective MVS systems. As a result, a library of RSCS NJE drivers appeared early that could translate JES2 formats into whatever was acceptable by the JES2 on the other end. JES2 eventually got around shipping support for 999 nodes ... but it was after the internal network had exceeded 1000 nodes. misc. past posts mentioning internal network http://www.garlic.com/~lynn/subnetwork.html#internalnet eventually the company stopped shipping the RSCS native drivers to customers ... just the NJE drivers ... although the native RSCS continued to be used internal ... in part because they were much more efficient and had higher throughput. person at the science center responsible for RSCS & internal network http://en.wikipedia.org/wiki/Edson_Hendricks from above: Meanwhile, in the fall of 1974, IBM announced System Network Architecture (SNA) as its official communications strategy. SNA was incompatible with VNET and with many of the networking ideas being developed for what would be called the Internet, particularly with TCP/IP. Hendricks and others lobbied vigorously within IBM for a change in direction, but were rebuffed. In 1976, MIT Professor Jerry Saltzer accompanied Hendricks to DARPA, where Henricks described his innovations to the principal scientist, Dr. Vinton P. Cerf. From that point on, Vint and other DARPA scientists adopted Hendricks' connectionless approach. The result developed into the Internet as we know it today. ... snip ... note that tcp/ip is the technology basis for the modern internet, NSFNET backbone was the operational basis for the modern internet, and CIX was the business basis for the modern internet. Some past posts http://www.garlic.com/~lynn/subnetwork.html#nsfnet NSFNET backbone originally started out to be interconnection of the NSF supercomputer and we were to get $20M to do it. Congress cuts the budget and various other things happen and it gets reformed and an RFP is released. Internal politics get in the way and prevents us from bidding. The director of NSF tries to help and writes a letter to the corporation, copying the CEO ... but that just aggravates the internal politics (references to things like what we already had running is at least five years ahead of all bid responses doesn't help). misc. old email http://www.garlic.com/~lynn/lhwemail.html#nsfnet -- virtualization experience starting Jan1968, online at home since Mar1970 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
