Chris Mason wrote:
I'm not sure at all about your comparison of IP and SNA with regard to ease
of routing. When I see the mess that Cisco types get up to in their "forum"
to which I subscribe,[1] IP doesn't look so easy after all. If you are
comparing IP and *subarea* SNA, you might have a - rickety - leg to stand
on. If you are comparing IP and *APPN/HPR* SNA, you'd be left in the dust -
from a theoretical standpoint - wildly mixing my linguistic metaphors. <g>
Unfortunately APPN/HPR came along too late to save the commercial world from
the horrors of IP.
my wife had co-authored awp39, peer-to-peer-networking in the same time-frame
as sna
starting ... minor topic drift:
http://www.garlic.com/~lynn/2006x.html#8 vmshare
which resulted in her taking a lot of heat from the sna organization. this
continued
when she was con'ed into going to pok to be in charge of loosely-coupled
architecture.
while there she authored peer-coupled shared data architecture ... which except
for IMS hot standby
didn't see much uptake until sysplex ... the battles with sna organization continue
... somewhat with a compromise that sna had to be used for anything crossing the boundaries
the glass-house. misc past posts mentioning peer-coupled shared data
architecture
http://www.garlic.com/~lynn/subtopic.html#shareddata
appn was awp164 ... and the sna organization non-concurred with announcing
appn. after six
weeks escalation, the appn/awp164 announcement letter was carefully rewritten
to make sure that nobody would be confused about there being any relationship
between appn/awp164 and sna. recent
posts mentioning awp164:
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/2006k.html#21 Sending CONSOLE/SYSLOG To
Off-Mainframe Server
http://www.garlic.com/~lynn/2006l.html#45 Mainframe Linux Mythbusting (Was:
Using Java in batch on z/OS?)
work started on tcp/ip in 1973 ... when it was recognized that arpanet was
inadequate ...
see reference to rfc801 in this post
http://www.garlic.com/~lynn/2007b.html#5 How many 36-bit Unix ports in the old
days?
the cut-over from arpanet to tcp/ip protocol was 1jan83 ... in the arpanet
newsletter
from jul80 ... see copy here
http://www.garlic.com/~lynn/2006r.html#7 Was FORTRAN buggy?
projected that there would be 100 (arpanet) nodes by 1983. This was
the year that the internal network
http://www.garlic.com/~lynn/subnetwork.html#internalnet
passed 1000 nodes. note that the internal network was NOT sna. post
that includes announcement of 1000th node
http://www.garlic.com/~lynn/99.html#112
http://www.garlic.com/~lynn/internet.html#22
and post
http://www.garlic.com/~lynn/2006k.html#43 Arpa address
with old email about getting ready for the 1000th node
http://www.garlic.com/~lynn/2006k.html#email830422
there were issues later with misinformation being pushed up to corporate
executives
as part of effort to convert internal network to SNA ... post
http://www.garlic.com/~lynn/2006x.html#7 vmshare
with old email about some of the misinformation being pushed up to corporate
executives
http://www.garlic.com/~lynn/2006x.html#email870302
another post about misinformation
http://www.garlic.com/~lynn/2006w.html#21 SNA/VTAM for NSFNET
----------------------------------------------------------------------
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
