Chris Mason wrote:
Radoslaw
My intention here was merely to point out that SNA and Ethernet are not
equivalent.
And I wanted to give some example to confirm your words.
[...]
You talk about print servers. I'm very vaguely familiar with the
principles of print and file servers [...]
I meant "hardware print server" - *usually* small & cheap appliance with
two ports: LPT and (Fast) Ethernet. Very limited configuration options,
usually it support "current version of Windows". I doubt if they still
support IPX, very popular LAN protocol few years ago. I have never seen
any box which even mentioned in documentation word "SNA".
[...]
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.
IP routing is basic function of any router. Every network guy is able to
make it working. APPN/HPR requires:
a) changes in VTAM configuration
b) selected network equipment
c) rare knowledge about non-IP networks.
Usually all the non-IP protocols are omitted on courses as it's
considered fading technology. This includes IPX, DNA (DECnet), SNA.
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
