Mainframe vs. xSeries 3284

misc. historical references of breastan & cambridge univ.

it was a 370-165 installed in 1971 (pre 370 virtual memory).

following has early 70s time-line (at the end of the post)

retrofitting virtual memory hardware to 165 ... to turn it into 165-II, cost a couple hundred thousand.

the cambridge references somewhat mentions difficulty in using (card-punch) JCL and-or "TSO" ... which appears to be motivating factor in the university developing the "phoenix command language".

something similar might be said of Stanford Univ. with Orville and Wylbur ... minor reference:

os-360 (or its 370 descendents) weren't particularlly noted for integrity infrastructures. in fact, hasp for much of its early life

was started as a normal application, "took over" the interrupt vector and intercepted all the interrupts to filter the stuff it was emulating. part of the issue was that most batch operations were closed operations and the "online" operations tended to be applications that provided only limited and very controlled feature-function.

by comparison, Univ. of Mich. had done MTS (michigan terminal system) utilizing virtual memory on 360-67 ... and then ported to 370 when 370 virtual memory feature became available.

also, there were the commercial time-sharing services using cp67-cms (on 360-67) later moved to virtual memory 370s

which required a very high level of privilege isolation and protection. similarly, the "cambridge" science center

provided online access to various internal corporate operations (including corporate hdqtrs business planning that used the system to analyze the most sensitive of corporate information) as well as providing online access to various professors and students in the boston area (aka the other cambridge).

--