|
I agree. Go with native TCP/IP. You get more options, all the usual suspects, like WRQ Reflection, Personal Communications, Synapse, Client Access, NetManage Rumba, various ODBC and OLE/DB drivers, etc. What benefit is there with SNA Server, other than connectivity? At 10:01 AM 3/20/02 -0800, you wrote: >Dare, > >In this day and age, an SNA gateway represents a huge overhead with >unnecessary complexity. Scrub the hard disk and set it up as a Linux >play pen! > >You'll find your network easier to manage if you remove the gateway and >go direct to the AS/400. > >IMHO > >Best Regards > >Fritz Hayes >Atwater Associates > ><snip> >| >| I forgot about my SNA Server. All client pass through this server to >get >| to >| the AS/400 >| > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.