The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main,alt.folklore.computers as well.


[email protected] (Paul Gilmartin) writes:
> I often wonder whether a reason TCP/IP triumphed over SNA was
> that SNA didn't provide a facility with the scalability of DNS.

re:
http://www.garlic.com/~lynn/2009q.html#82

in some ways ... SNA is even less general than the arpanet
implementation prior to the cut-over to internetworking on 1/1/83
... which DNS is one part of. 

misc. trivia ... the person responsible for DNS had earlier spent some
time at the science center ... some science center posts
http://www.garlic.com/~lynn/subtopic.html#545tech

when the person was student at mit.

tcp/ip was the technology basis for the modern internet ... nsfnet
backbone was the operational basis for the modern internet and cix was
the business basis for the modern internet. misc. old email related
to nsfnet backbone:
http://www.garlic.com/~lynn/lhwemail.html#nsfnet

one of the things that the internal networking technology did was a kind
of gateway facility in every node ... somethat that was also was a
feature of internetworking. misc. past posts mentioning internal network
http://www.garlic.com/~lynn/subnetwork.html#internalnet

JES2 had other significant issues ... having muddled what was job
control and what was networking. as a result ... JES2 systems at
different levels and with incompatible headers ... could crash each
other ... and bring down the whole system (there was infamous case of
some internal jes2 systems in san jose which were bringing down hursley
mvs systems).

the major internal networking technology was able to have "native"
drivers ... but also install "jes2" drivers for communicating with jes2
systems (and allow jes2/mvs systems to participate in the internal
network). this feature evolved into these (non-native) jes2 drives
adding features to try and rewrite jes2 headers to that they were always
compatible with the direclty connected jes2/mvs systems (as
countermeasure to have high frequency of jes2/mvs crashing all over the
world). the internal technology got blaimed for not preventing the
hursley mvs systems from crashing (since the internet network technology
hadn't been upgraded to filter some of the new san jose jes2 fields
... from reaching the hursley jes2 systems). misc. past posts mentioning
hasp, jes2, and/or jes2 networking
http://www.garlic.com/~lynn/submain.html#hasp

dislcaimer: my wife did a stint in the jes group (among other things
acted as one of the catchers for asp->jes3 ... and did a design document
for merged jes2/jes3 product) ... before getting con'ed into going to
pok to be in charge of loosely-coupled architecture.

my wife was also co-author of internal architecture document (AWP39) in
the early days of SNA called peer-to-peer networking (which SNA group
possible viewed as competition to their master/terminal-control
architecture). she also had numerous battles in POK with the SNA
organization over not using SNA for her "peer-coupled shared data
architecture" (which, except for ims hot-standby, saw very little uptake
until sysplex) ... some past references:
http://www.garlic.com/~lynn/submain.html#shareddata

there were temporary truces with the SNA organization over her not
having to use SNA within the walls/boundaries of the datacenter ... but
SNA had to be used if something involved crossing the datacenter walls.

later i would needle the person responsible for APPN (AWP164) to stop
trying to prop up SNA (they weren't going to appreciate it) and come
work on real networking ... if fact, the SNA organization non-concurred
with announcing APPN ... and it was held up for several weeks while the
announcement letter was careful to not even imply that there was any
connection between APPN and SNA.

misc. past posts mentioning AWP39, AWP164 &/or AAPN
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/2007b.html#49 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
http://www.garlic.com/~lynn/2007o.html#72 FICON tape drive?
http://www.garlic.com/~lynn/2007p.html#12 JES2 or JES3, Which one is older?
http://www.garlic.com/~lynn/2007p.html#23 Newsweek article--baby boomers and 
computers
http://www.garlic.com/~lynn/2007q.html#46 Are there tasks that don't play by 
WLM's rules
http://www.garlic.com/~lynn/2007r.html#10 IBM System/3 & 3277-1
http://www.garlic.com/~lynn/2007v.html#53 folklore indeed
http://www.garlic.com/~lynn/2008b.html#42 windows time service
http://www.garlic.com/~lynn/2008d.html#71 Interesting ibm about the myths of 
the Mainframe
http://www.garlic.com/~lynn/2008e.html#73 Convergent Technologies vs Sun
http://www.garlic.com/~lynn/2008i.html#97 We're losing the battle
http://www.garlic.com/~lynn/2009e.html#56 When did "client server" become part 
of the language?
http://www.garlic.com/~lynn/2009i.html#26 Why are z/OS people reluctant to use 
z/OS UNIX?
http://www.garlic.com/~lynn/2009l.html#3 VTAM security issue
http://www.garlic.com/~lynn/2009l.html#7 VTAM security issue

-- 
40+yrs virtualization experience (since Jan68), online at home since Mar1970

----------------------------------------------------------------------
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

Reply via email to