RE: SNA over TCP/IP

Chris:
I agree, SNADS is rock solid.  I still prefer some SNA stuff for some
things.  On our internal network, ALL the DDM traffic is still defined as
SNA not IP.  I see no good reason to change.  Now, I would NEVER advocate we
go back to SNA for terminal emulation or other things, but SNA is/was ROCK
SOLID.
cjg

Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw Avenue, Suite 800
Marietta, GA  30060
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:cgalgano@xxxxxxxxxxxxxxxxx
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and
Implementation 
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight

"You ain't gonna learn what you don't want to know" - rw

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Thursday, June 12, 2003 10:38 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: SNA over TCP/IP


Once I had to send a 2GB save file across a WAN.  This was a 128k private
Frame Relay connection.  We also have a 56K PTP Leased line from V.35 to
V.35 on the two AS400's.  Because of the FR being 2+ times faster and FTP
has less overhead than SNADS, I thought that I would FTP the file.  After
two attempts failed 2hrs into transmission, with no recovery possible,  I
decided to SNADS the file.  Took 4 hours and completed with out a hitch.  I
now am running *anynet over the FR and SNADS works great.  FTP still fails
about half way thru.  Seems our carrier has issues with us pushing data past
our purchased rate which our routers will use all available band with on the
FR circuit.  Yes the SNADS get interrupted during the transfer but does not
drop, it RECOVERS and CONTINUES.  FTP drops the connection and it is back to
square one.

Chris Bipes