| Newsgroups |
gmane.comp.emulators.hercules390.mvs |
| Message-ID |
<[email protected]> |
Hi Brian,
>1) The device type in your HCD of x'e20' it should be CTC, if not, use a address that is CTC
According to ISPF M.4, it is.
>2) The IP of your router (this is the gateway in TCPIP on z/OS) 192.168.1.yyy
192.168.1.1
>3) The IP of your windows PC (or whatever OS you are running) 192.168.1.www
192.168.1.101 (Windows 10)
>4) The IP of your Hercules z/OS instance 192.168.1.xxx
192.168.1.201
>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
Running IBM MVS TCP/IP CS V2R1 TCP/IP Configuration Tester
The FTP configuration parameter file used will be "TCPIP.FTP.DATA".
TCP Host Name is: ZOS
Using Name Server to Resolve ZOS
The following IP addresses correspond to TCP Host Name: ZOS
192.168.1.201
The following IP addresses are the HOME IP addresses defined in PROFILE.TCPIP:
192.168.1.201
127.0.0.1
All IP addresses for ZOS are in the HOME list!
Hometest was successful - all Tests Passed!
***
>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
I now have:
DEVICE LCS1 LCS E20 AUTORESTART
LINK ETH1 ETHERNET 0 LCS1
HOME
192.168.1.201 ETH1
BEGINRoutes
ROUTE 192.168.0.0 255.255.0.0 = ETH1 MTU 1492
ROUTE DEFAULT 192.168.1.1 ETH1 MTU 1492
ENDRoutes
START LCS1
>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
>
I have:
TCPIPJOBNAME TCPIP
HOSTNAME ZOS
DOMAINORIGIN MANASYS.CO.NZ
DATASETPREFIX TCPIP
NSINTERADDR 192.168.1.1
RESOLVEVIA UDP
RESOLVERTIMEOUT 10
RESOLVERUDPRETRIES 1
LOOKUP LOCAL DNS
ALWAYSWTO NO
>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)
192.168.1.201 ZOS
192.168.1.101 DESKTOP
192.168.1.1 ROUTER
>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
DEFAULTTCPIPDATA('USER.TCPPARMS(TCPDATA)')
GLOBALTCPIPDATA('USER.TCPPARMS(TCPDATA)')
GLOBALIPNODES('USER.TCPPARMS(GBLIPNOD)')
DEFAULTIPNODES('USER.TCPPARMS(GBLIPNOD)')
COMMONSEARCH
CACHE
CACHESIZE(200M)
MAXTTL(2147483647)
UNRESPONSIVETHRESHOLD(25)
>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.
I have:
0E20-0E21 LCS -n 192.168.1.101 -m 02-AA-BB-CC-DD-EE 192.168.1.201
>…TN3270…
I don’t use TN3270
>Incidentally, Fish's code works perfectly fine with WiFi adapters…
For me this is a trade-off between stability and capability. The Wi-Fi adapter connection is stable but won’t allow me to ping the router from the guest, so nothing gets resolved. The onboard nic (cable) connection is the opposite: it will die easily – even with one attempt at a binary transfer – but I can ping www.softdevlabs.com from ISPF 6 without a problem.
>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.
HOMETEST tells me some things, but not nearly enough to fix my problem.
>Let me know if you have any other questions.
What does TN3270 have to do with FTP (apart from them both using TCP/IP)?
>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.
I haven’t really made any changes, as I already had pretty-much what you suggested. I made some cosmetic changes anyway, but it has made no difference. I suspect that as the greatest variable seems to be the difference in behaviour of the Wi-fi and cable connections that there is something I need to do differently with the adapter settings – the offload stuff perhaps. I can’t see any offload settings at all for the Wi-fi card. The other non-Wi-Fi card has ARP Offload and NS Offload, both of which I have set to Disabled, again making no difference.
I really appreciate you taking the time to look at this.
Thanks,
Peter