IBM 360 channel buttignments 524

Rob Warnock small-but-useful byte better to this

for 3380 drives, they introduced data streaming. selector & byte multiplexor had bus&tag syncronous hand-shake on every byte ... that limited normal stuff to about 200' and something like 2301 drum (over 1mbyte-sec) to maybe 70-80".

data streaming up that to 8bytes and supported 3mbyte-sec up to 400' (later raised to 4.5mbyte-sec).

part of the problem with escon (fiber 200mbit-sec) is that it tended to preserve the end-to-end half-dupliex operation. escon had been laying around pok for quite some time before it saw the light-of-day. one of the rs-6000 engineers took the basic escon ... up'ed it to 220mbit-sec, used much cheaper optical drivers and made it full-duplex ... which was announced as serial-link adapter (SLA) for rs-6000.

we had been going to hippi and fcs meetings and when the engineer started looking at moving sla to 800mbit ... we talked him in working on fiber-channel standard instead. he became editor of the FCS document. one of the issue in FCS was some number of the pok channel engineers were participating in the standards meetings and they were constantly trying to overlay the escon half-duplex operational model on basically a full-duplex operation.

misc. past post mentioning data-streaming "multiplexers"? language for OS-390 ? count shrinking = bad performance length-distance? Why ? with TCP-IP? ending characters begin? architectures use instruction Metrics security both crypto and non-crypto?