| Newsgroups |
gmane.comp.emulators.hercules390.general |
| Message-ID |
<[email protected]> |
Why the concern about resolver if you can’t ping zOS from the windows pc? If you can’t ping you have a routing issue on either windows and/or zOS.
I’d suggest reading the red book on zpdt on network setup. It’s the same setup for both zpdt and Hercules.
Sandra
Sent from my iPhone 7 Plus
> On Jun 2, 2019, at 9:32 AM, gheorghedragos1988-/[email protected] [hercules-390] <[email protected]> wrote:
>
>
>
> Dear Brian,
>
> I waned to contact you via private mail ( if that would have been appropriate ), however, I couldn't find a way to do so. So I will write here, with the risk of antagonizing some of our colleagues ( for good reason I am sure ) .
>
> I have managed to define and start resolver as a STC, and copied all required parameters from TCPIP.SEZAINST dataset ( the default ones.. ). Here is the startup on the console :
>
> 00- 08.11.46 STC00838 $HASP373 RESOLVER STARTED
> 08.11.46 STC00838 EZZ9298I DEFAULTTCPIPDATA -
> ADCD.Z113S.TCPPARMS(TCPDATA)
> 08.11.46 STC00838 EZZ9298I GLOBALTCPIPDATA - ADCD.Z113S.TCPPARMS(TCPDATA)
> 08.11.46 STC00838 EZZ9298I DEFAULTIPNODES - ADCD.Z113S.TCPPARMS(IPNODES)
> 08.11.46 STC00838 EZZ9298I GLOBALIPNODES - ADCD.Z113S.TCPPARMS(IPNODES)
> 08.11.46 STC00838 EZZ9304I NOCOMMONSEARCH
> 08.11.46 STC00838 EZZ9304I CACHE
> 08.11.46 STC00838 EZZ9298I CACHESIZE - 200M
> 08.11.46 STC00838 EZZ9298I MAXTTL - 2147483647
> 08.11.46 STC00838 EZZ9298I UNRESPONSIVETHRESHOLD - 25
> 08.11.47 STC00838 EZZ9291I RESOLVER INITIALIZATION COMPLETE
>
> While doing TSO hometest, session got stuck, and console shows me :
>
> *EZZ9308E UNRESPONSIVE NAME SERVER DETECTED AT IP ADDRESS 192.168.0.1
> EZZ9310I NAME SERVER 192.168.0.1 724
> TOTAL NUMBER OF QUERIES SENT 1
> TOTAL NUMBER OF FAILURES 1
> PERCENTAGE 100%
> EZZ9309I NAME SERVER IS NOW RESPONSIVE AT IP ADDRESS 192.168.0.1
> EZZ9310I NAME SERVER 192.168.0.1 726
> TOTAL NUMBER OF QUERIES SENT 0
> TOTAL NUMBER OF FAILURES 0
> PERCENTAGE 0%
>
>
> The problem might be, is that I cannot even pin 192.168.0.1 from Hercules.. I can only ping 192.168.0.122 ( windows ). Therefore, I think some windows routing might need to be done.
> The configuration of the globaltcpipdata, ipnodes etc have been done as instructed.
>
> I propose we stop the conversation on this topic, as in this place is a little bit off subject.
>
> Dragos
>
>
>
>
>
>