virtual memory 4489

re:

"811" (named after 11-78 publication date on the architecture documents) or 3081 was considered somewhat of a 155-158 follow-on machine ... being much more of a m'coded machine.

"TROUT" or 3090 was considered somewhat of a 165-168 follow-on machine ... being much more of a hardwired machine.

these were the days of processors getting bigger and bigger with much more effort being put into more processors in SMP configuration.

they had created two positions, one in charge of "tightly-coupled" architecuture (SMP) and one in charge of "loosely-coupled" architecture (clusters). my wife got con'ed into taking the job in pok in charge of loosed-coupled architecture.

she didn't last long ... while there, she did do done peer-coupled shared data architecture

which didn't see much uptake until sysplex ... except for the ims group doing ims hot-standby.

part of the problem was she was fighting frequently with the communication's group, who wanted SNA-VTAM to be in charge of any signals leaving a processor complex (even those directly to another processor).

one example was trouter-3088 ... she fought hard for hardware enhancements for full-duplex operation. there had been a previous "channel-to-channel" hardware which was half-duplex direct channel-bus communication between two processor complexes. 3088 enhanced this to provide connectivity to up to eight different processor complexes.

sna was essentially a dumb terminal controller infrastructure. their reference to it as a "network" required other people in the organization to migrate to using the term "peer-to-peer network" to differentiate from the sna variety.

of course, earlier, in the time-frame that sna was just starting out ... she had also co-authored a peer-to-peer networking architecture with Burt Moldow ... which was somewhat viewed as threatening to sna ... misc. past posts mentioning awp39:

anyway, in the trotter-3088 time-frame ... san jose had done a prototype vm-cluster implementation using a modified trotter-3088 with full-duplex protocols. however, before it was allowed to ship, they had to convert it to san operation. one of the cluster example was to fully "resynch" cluster operation of all the processors ... with took under a second using full-duplex protocols on the 3088 ... but the same operation took on the order of a minute using sna protocols and a half-duplex paradigm.

we ran afoul again later with 3-tier architecture

this was in the time-frame that the communications group was out pushing SAA ... a lot of which was an attempt to revert back to terminal emulation paradigm

from that of client-server. we had come up with 3-tier architecture and was out pitching it to customer executives ... and the same time they were trying to revert 2-tier architecture back to dumb terminal emulation.

then we did ha-cmp product

minor reference

which didn't make a lot of them happy either.

--