×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
If you have communication links (mostly the 'old' way, using SNA), the
system name is part of the communication configuration. Not so much of
an issue with Ethernet.
I don't understand what you're saying here. SNA is a protocol; Ethernet is
a medium. Comparing SNA against Ethernet is like comparing blue against
boats. (I am reminded of the old quote: "A man without religion is like a
fish without a bicycle.")
So you know, one can run SNA protocol over Ethernet; we used to do that all
the time between our midrange and mainframe systems. One can also run
TCP/IP over old-style communications lines (although tunneling may be
involved).
The point to understand is that NETA values do not apply to TCP/IP. While
one may make the hostname match the SNA network attributes, this is not
mandated, and in fact is not usually even a good idea. (Think backup routes
et cetera.)
Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"Advice is what we ask for when we already know the answer but wish we
didn't."
-- Erica Jong
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
