RE: LCS connection dies

I'm coming into this late so if I ask something that you already answered please be patient.
 

 First I need some information from you.
 

 1) The device type in your HCD of x'e20'  it should be CTC, if not, use a address that is CTC

 2) The IP of your router (this is the gateway in TCPIP on z/OS)  192.168.1.yyy

 3) The IP of your windows PC (or whatever OS you are running)  192.168.1.www

 4) The IP of your Hercules z/OS instance 192.168.1.xxx

 

 I'm going to ask you to go back to LCS in TCPIP, but before you make changes, please execute a HOMETEST command under TSO.  (If inside ISPF type "TSO HOMETEST") and post the results here
 

 in your TCPIP profile member you should have  (assuming E20 is valid)

 

  DEVICE LCSA1  LCS   E20  AUTORESTART
 LINK   LCS1   ETHERNET   0 LCSA1
 

 HOME
192.168.1.xxx   LCS1     (where xxx is the IP of z/OS (#4 above)
 

 

 BEGINROUTES
 ROUTE   192.168.0.0  255.255.0.0  =  LCS1 MTU 1492
 ROUTE   DEFAULT      192.168.1.yyy    LCS1 MTU 1492   (where yyy is your router)
ENDROUTES
 

 (note above that I have 192.168.0.0 not 192.168.1.0 as you have in your current profile.)
 

 START LCSA1
 

 

 You TCPIP TCPDATA member isn't listed, but needs to be:
 

 HOSTNAME Z23   (Z23 should be whatever your current hostname is in your commandxx member)
                         the commndxx member should have a line COM='S EZAZSSI,P=Z23'
                            where the Z23 is what is in mine, your might be something else

 

 DOMAINORIGIN  your.local.domain  (this can be a web site that you own)

 

  NSINTERADDR  192.168.1.yyy  (again yyy is your router)
 

 RESOLVEVIA UDP
 

   LOOKUP LOCAL DNS
 

 You MUST run RESOLVER under z/OS and the resolver parms should be:
 

 IPNODES member
 

    192.168.1.xxx  Z23 (again xxx is your z/OS instance, and Z23 is whatever you put in the hostname entry above)
 

 RECOLVES member
 

  DEFAULTTCPIPDATA('Z23.TCPPARMS(TCPDATA)')  <--this needs to point to you TCPDATA member
                                                                                mine is 'z23.tcpparms(tcpdata)'

  GLOBALTCPIPDATA('Z23.TCPPARMS(TCPDATA)')  <-- same place

 

  GLOBALIPNODES('Z23.TCPPARMS(IPNODES)')   <---  this points to the IPnodes member above

 

  DEFAULTIPNODES('Z23.TCPPARMS(IPNODES)'))  <--- same place
 

 

 Your hercules CONFIG member needs to contain:
 

 0E20-0E21    LCS     -n 192.168.1.www -m 02-AA-BB-CC-DD-EE 192.168.1.xxx
                 www is your Windows PC IP and xxx is the z/OS instance
                 the MAC address 02-aa-bb-cc-dd-ee should be coded exactly as it is here its a dummy address
                      but in nonetheless necessary.
 

 You will also need to make sure your TN3270 parms are set correctly, if you post your TN3270 member I can tell you if you have errors.
 

 What I have noticed a lot is that people will "attempt" to set up TCPIP under hercules, and then they try to use it via a VTAM terminal instead of a TN3270 session terminal.  Or they try to use FTP when they don't even have TN3270 running yet and to expect FTP to work when you haven't got TN3270 correct yet is ridiculous.

 

 If you are using Vista 3270 emulator and you have TV3270 up and running under z/OS (a lot of people leave that part out as well).  When you set up the Vista 3270 session, the IP you want to use is 192.168.1.xxx  (xxx is your IP of the z/OS instance, not your PC or the router) and you need to specify port 23.
 

 You also need to make sure you have WinPcap and  Fish's CTCI installed.  Fish's install will normally install WinPcap.  

 

 So, if you make the above changes and if your system has a CTC defined at E20 and if you have CTCI installed correctly with WinPcap, then everything will work perfectly.
 

 Incidentally, Fish's code works perfectly fine with WiFi adapters, it just needs to be the first (or only) one defined if you are going to use one, and make sure you turn off the offload features of your adapters.  If you have a real ethernet adapter on your PC, it will likely be first so your wifi adapter will probably not be stable.  If you always use wifi, then remove or disable you ethernet adapter in your bios and the WiFi one will work fine.
 

 If you follow the above directions, it will work, just be careful of typo's.
 

 You will know you have everything correct if you execute HOMETEST and it tells you everything is where it needs to be.  Otherwise, fix whatever it tells you is not correct.
 

 Let me know if you have any other questions.  When you are done, it would be helpful if you posted all of your changes so that other people who might want to do this themselves can see your "actual" working changes and will know what to do on their system.  

 

 When it's all done correctly it will work and you will wonder why you didn't do all of this sooner.  It's very easy to get caught up in the network setup and forget when TCP applies and when VTAM applies to what is happening under z/OS to make the network work.  You can't expect this to work without configuring both VTAM (which I didn't cover here, but I can if you need it) and TCPIP.  And once it's set up correctly, it will work very efficiently every time you IPL the system.  It might seem difficult, but mostly that's because I am jsut telling you what to do and not why.  The why would  make things easier to understand, but I type bad enough as it is, so it's best I don't try to explain too much. :)

 

 Brian