RE: LCS connection dies

Hi,
 

 "Pretty much" won't cut it, you really need to code what I specified.  The reason your sessions are dropping when you try to send data is because you are not passing the tcpip datagrams correctly, that's what we are trying to fix.  I have helped close to 100 people set this up and I have not failed yet.  Some took longer to realize that they can't assume they had parts right because when you tell me you have something coded a certain way, I tend to believe you and if you didn't actually code it right it can waste a lot of time.  I have actually posted the steps several times and recently I have asked people to post there configurations once they get it right, (and several have posted it), so you really should have some samples to copy and they are all types of setups, some VM, some Windows, some Linux, and some Macs.

 

 The reason you should set up TN3270 first is because it's easier than FTP and will tell us if you have something wrong, whereas FTP is finicky and can't be easily debugged like TN3270 can.
 

 already I can see that you have a error in IPNODES that will cause you to loop incorrectly, so take both

 

 192.168.1.101 DESKTOP 
192.168.1.1 ROUTER 

 

 out of IPNODES.  I don't know why you coded them and they don't belong there and will cause a problem all by themselves.  Actually you are using 'USER. TCPPARMS( GBLIPNOD) ' so that's the member you will need to change.

 

 So, post your resolver members (the ones pointed to in your RESOLVER proc), and the same for OMPROUTE
 

 Also post your entire TCPIP profile and TCPDATA members as well as the actual procs for TCPIP and RESOLVER and OMPROUTE.

 

 Also, just because you can ping one way or the other has nothing to do with having things set up correctly.  Don't assume that you have anything right unless you can go both ways all the time, anything less is not right.
 

 Using a Ethernet adapter or Wifi are equally stable, I use wifi on my laptop to run hercules and a ethernet adapater on my desktop, they are both completely stable, and in fact I can connect them together and I can NJE and run EE between the two systems with no problems.
 

 Offload is not going to be your current problem.  It will only make a difference if you start to send large amounts of data and I don't think that even then it will matter so long as you a re using the first adapter in your system.

 

 One of the problems that many people have had with Hercules setup with TCPIP is that they muck around a lot and it's mostly a matter of undoing the stuff they changed.  There are a lot of things that will seem to be okay, but actually are not.  It's like a small puzzle and the pieces will really fit together only one way, but they are such that it might seem like they fit even though they are merely "close" to fitting. 

 

 This is set up exactly as you would on a real mainframe with real devices, so there is a large volume of information on what each of the parms is for and how to connect them.
 

 In the end though, if you don't want my help, just say so, but complaining that there is something wrong with Hercules or z/OS is just plain wrong.  There is a slight chance that one of your adapters is defective, but the chances are low that they both are, and I assume that you are able to use at least one of them to access this list so you should be able to get this working on that adapter.

 

 Brian