Sending CONSOLESYSLOG To OffMainframe Server
we were periodically constantly fighting with the communications group. the communications group had set up sna as communication control of large number of terminals ... but the included "network" in their label ... which little or nothing to do with what it was doing.
this somewhat forced other organizations to adapt nomenclature like "peer-to-peer networking" to describe real networking and differentiate it from sna. early in sna lifetime, my wife co-authored peer-to-peer networking AWP39 architecture with Bert Moldow ... which put them at odds with the communication organization.
she then got con'ed into going to POK to be in charge of loosely coupled architecture ... where she created "peer-coupled shared data" architecture
the communication group was constantly trying to carve off as their turf any bits that left the processor complex ... even purely processor-to-processor communication, creating lots of difficulties for my wife. recent comment on one such involving 3088-trotter
the communication group did contribute to early update of PCs with terminal emulation ... for about the same price as a mainframe terminal, a person could get a single desktop footprint (keyboard and display) that did both mainframe connectivity and local computing.
however, in the late 80s, "peer-to-peer" networking and client-server was emeging for PCs ... and the communication group was attempting to counter it with SAA ... attempting to maintain as much as possible the earlier terminal emulation paradigm
it was in this period that we had created 3-tier architecture and were out pitching it to customer executives
and were taking a lot of heat from the communication group and SAA forces.
Can anythink kill x8664
they sold IBM PCs in lieu of mainframe terminals (at about the same price) ... as part of this, the communication group acquired a big install base of terminal emulation products the millions of...
during the 80s, the communication-sna group had also done things like non-concurred with the announcement of APPN ... i.e. AWP164 ... recent post mentioning APPN-AWP164 (as well as AWP39): with an IP address to the mainframe
for a little drift, thread talking about the internal network (going on in the same period as arpanet):
Alt Folklore Computers Newsgroups