|
Hank, We are using AnyNet on about 300 NT workstations. The performance is hard to judge because we haven't really used anything else. To me, it is fine. I'm even using it on a 486-66 with 36 megabytes of RAM. We sometimes have intermittent connection failures, but these have decreased with each service pack of Client Access. We don't create the devices on the system manually. They are automatically created during the first connection to the AS/400. The only thing we had to do on the AS/400 was configure an AnyNet controller and TCP/IP. The biggest negative that I have about it is using the NetSoft router. The 16bit version was fine but this 32bit version has been the source (I believe) of most of our communication problems. We are wanting to use the straight TCP/IP version when the device id naming option is available (V3R1M3 of CA). Good luck, Mark Welte ---------- From: HankHeath@aol.com[SMTP:HankHeath@aol.com] Sent: Thursday, February 05, 1998 9:00 PM To: MIDRANGE-L@midrange.com Subject: Fwd: Question on AnyNet Forwarded question from a colleague: << One of the critical pieces of our new application is a PC client tool that does data analysis & manipulation and shows the users pretty graphs of AS/400 data. Sticking point: it only runs SNA using NetSoft router provided w/Client Access. We only support TCP/IP across our wide area network, my Cisco routers won't route SNA. Now they have this brilliant idea: use AnyNet (now conveniently provided with OS/400) to encapsulate the SNA in IP, thus solving said problem and allowing us to run the existing client software. And conveniently getting them off the hook for making sure they deliver the IP version they claim is in the works on time. Question: ever been exposed to AnyNet? Work OK? Performance hog? Good idea, or stupid idea? I'm setting it up for a test, but any input you have would be appreciated. P.S. According to the config. instrux, you have to MANUALLY create all the device descriptions for the PCs on the 400. Eeeeeee! How primitive <g>. >> +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.