Re: Hercules networking problem...again

Okay here's an easy way to set this up.  Assuming that E22 and E23 are defined in your system and if you are really ADCD then it should be.  I think you used E20&21, but E22&23 on ADCD is there as well.

 

 In your config file specify:
 

 0E22-0E23    LCS     -n 192.168.0.120 -m 02-AA-BB-CC-DD-EE 192.168.0.122
 

 The -m part will create a dummy MAC address of 02-aa-bb-cc-dd-ee to be used.  It's required to make this work correctly, but the actual number/letters (so long as they are no larger than 'f') are up to you, the ones I have here will work and will most definitely not be in existence on your network right now.  The important part is that the first address is your windows IP and the last one is your hercules|Zos IP.

 

 In your TCP profile you need:

 

  DEVICE LCSA2  LCS   E22  AUTORESTART
 LINK       LCS2   ETHERNET   0   LCSA2

 

 ;HOME points to your Hercules instance of z/OS

 

   HOME
   192.168.0.122   LCS2
 

 
BEGINROUTES
 ROUTE   192.168.0.0  255.255.0.0  =  LCS2 MTU 1492
 ROUTE   DEFAULT      192.168.0.1    LCS2 MTU 1492
ENDROUTES
 

 START LCSA2
 

 The above will only use one of the links, but I'm sure you get the idea and one is more than enough for running on a PC.
 

 Remove all of the other DEVICE, LINK, START statements and if you actually have them in the order you specified in your post, you will need to change the START to after all of the other statements.
 

 Your TCPDATA parms shoudl have (at a minimum) the following:
 

 HOSTNAME Z23   ;or whatever you want to call your system, this  gets used in parmlib
                             ; in your COM='S EZAZSSI,P=Z23' of COMMNDxx member   

 

 DOMAINORIGIN  yourwebname.COM     ;assuming you have a DNS web name to point to

 

 ; Next is the Router gateway you use to get to the internet DNS server
 NSINTERADDR  192.168.0.1
 

 Your RESOLVER started task should point to the RESOLVES member of your current TCPPARMs dataset and should (at a minimum) contain:  (you will need to replace the "yourhlq" parts:

  DEFAULTTCPIPDATA('yourhlq.TCPPARMS(TCPDATA)')
  
 GLOBALTCPIPDATA('yourhlq.TCPPARMS(TCPDATA)')

 

  GLOBALIPNODES('yourhlq.TCPPARMS(IPNODES)')  <--and make sure it exists
 

  DEFAULTIPNODES('yourhlq.TCPPARMS(IPNODES)'))  <---same
 

 TCPPARMS(IPNODES) should contain:
 

    192.168.0.122   Z23      <--- this ties back to the hostname you decided to use
 ; this will keep you from having to rely solely on the HOSTS file stuff

 

 You will also need to fix your MAKESITE statements (hosts file in z/OS) to get rid of the 192.168.0.61.  Apparently at some time you generated the SITE with that address in it.  Once you do the changes I noted above, everything will work, except for sending and receiving email from your site which will need to have the hosts file changed.  The directions for that are part of the ADCD documentation, but you can just type "HELP MAKESITE" under TSO to get the directions.  There are three datasets involved in the process, you update one of them (hlq.hosts.local) via edit and you generate the other two ( hlq.HOSTS.SITEINFO and hlq.HOSTS.ADDRINFO) via the MAKESITE command. You should have all three right now probably with a HLQ of TCPIP or TCPIVP.  

 

 This should get you going, but if you have any other questions feel free to contact me on this site or via direct email.  I only occasionally monitor the site, but I check my email all the time.
 

 Brian