George McAliley wrote:
All IBM 3490's on mainframes were either Block MPX channel (bus/tag) or
ESCON. The STK 9490's on mainframe were also ESCON though they did have
a SCSI interface for distributed system attachment. The IBM Magstar (3590)
series were natively FICON and ESCON capable depending on how you
configure the drive/controller. The newer 3592's are also either ESCON or
FICON though they are really too fast for ESCON. All the Magstar drives have
standalone (non_ATL) configurations but are now usually installed in ATL's or
VTL's in today's world.
a recent escon, sla, fcs, ficon and eckd x-over discussion from comp.arch
newsgroup
http://www.garlic.com/~lynn/2007o.html#54 mainframe performance, was Is a RISC
chip more expensive?
and additional drift, other posts in the thread:
http://www.garlic.com/~lynn/2007o.html#42 mainframe performance, was Is a RISC
chip more expensive?
http://www.garlic.com/~lynn/2007o.html#55 mainframe performance, was Is a RISC
chip more expensive?
... escon had been fiber technology that had knocking around pok from
the 70s. my wife had been con'ed into going to pok to be in charge of
loosely-coupled architecture where she created peer-coupled shared data
architecture
http://www.garlic.com/~lynn/subtopic.html#shareddata
which didn't see a whole lot of take-up until sysplex ... except for ims
hot-standby work.
she also had significant battles with the communication group over not using
sna for peer-coupled operation. eventually there supposedly was a (temporary)
truce where sna had to be used for anything transiting the walls of the
glasshouse
but non-sna could be used within the walls of the glasshouse. this
sort of came to a test with ctca enhancement; trotter/3088 where she pushed
hard for being able to have full-duplex operation ... as improvement over
standard ctca/channel half-duplex operation (which didn't make it out
of the door).
san jose research did do a vm/4341 cluster prototype using enhanced 3088
peer-coupled operation ... but when it came to make it available to customers,
they were required to use sna for the implementation. a trivial
example of the difference was the cluster synchronization protocol ...
which started out being done in subsecond elapsed time. it was severely
crippled by being forced to regress to a sna implementation which increased
the cluster synchronization protocol elapsed time to nearly a minute.
all of this contributed to her not lasting very long as pok's loosely-coupled
architect. of course, part of her problem was that she had earlier co-authored
AWP39, peer-coupled networking architecture in the early days of SNA ... which
they possibly viewed as a threat. SNA architecture was VTAM ... not a networking
architecture at all, but a (dumb) terminal communication control infrastructure
that could handle massive numbers of terminals (or at least initially up to
64k). for other random trivia, appn was AWP164
misc. past posts mentioning AWP39
http://www.garlic.com/~lynn/2004n.html#38 RS/6000 in Sysplex Environment
http://www.garlic.com/~lynn/2004p.html#31 IBM 3705 and UC.5
http://www.garlic.com/~lynn/2005p.html#8 EBCDIC to 6-bit and back
http://www.garlic.com/~lynn/2005p.html#15 DUMP Datasets and SMS
http://www.garlic.com/~lynn/2005p.html#17 DUMP Datasets and SMS
http://www.garlic.com/~lynn/2005q.html#27 What ever happened to Tandem and
NonStop OS ?
http://www.garlic.com/~lynn/2005u.html#23 Channel Distances
http://www.garlic.com/~lynn/2006h.html#52 Need Help defining an AS400 with an
IP address to the mainframe
http://www.garlic.com/~lynn/2006j.html#31 virtual memory
http://www.garlic.com/~lynn/2006k.html#9 Arpa address
http://www.garlic.com/~lynn/2006k.html#21 Sending CONSOLE/SYSLOG To
Off-Mainframe Server
http://www.garlic.com/~lynn/2006l.html#4 Google Architecture
http://www.garlic.com/~lynn/2006l.html#45 Mainframe Linux Mythbusting (Was:
Using Java in batch on z/OS?)
http://www.garlic.com/~lynn/2006o.html#62 Greatest Software, System R
http://www.garlic.com/~lynn/2006r.html#4 Was FORTRAN buggy?
http://www.garlic.com/~lynn/2006r.html#9 Was FORTRAN buggy?
http://www.garlic.com/~lynn/2006t.html#36 The Future of CPUs: What's After
Multi-Core?
http://www.garlic.com/~lynn/2006u.html#28 Assembler question
http://www.garlic.com/~lynn/2006u.html#55 What's a mainframe?
http://www.garlic.com/~lynn/2007b.html#9 Mainframe vs. "Server" (Was Just
another example of mainframe
http://www.garlic.com/~lynn/2007b.html#48 6400 impact printer
http://www.garlic.com/~lynn/2007d.html#55 Is computer history taugh now?
http://www.garlic.com/~lynn/2007h.html#35 sizeof() was: The Perfect Computer -
36 bits?
http://www.garlic.com/~lynn/2007h.html#39 sizeof() was: The Perfect Computer -
36 bits?
http://www.garlic.com/~lynn/2007l.html#62 Friday musings on the future of 3270
applications
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
