Jorge Well, I'm glad you've worked it all out.
Now the only mystery for those following this thread in the list is how your F RESOLVER,DISPLAY and //SYSTCPD DD DSN=...(TCPDATA) do *not* correspond to the "resolver trace" output you posted before! I even found where that output is explained - the z/OS Communications Server IP Diagnosis Guide manual - just to make sure I had interpreted it correctly. Chris Mason On Mon, 10 May 2010 03:02:09 -0500, Jorge Garcia <jgarc...@mapfre.com> wrote: >Hello Chris: > >>An example from the z/OS Communications Server IP System Administrators >>Commands description of the "MODIFY command: Resolver address space": > >Sorry. The command works. > >F RESOLVER,DISPLAY >EZZ9298I DEFAULTTCPIPDATA - SYS2.TCPIP.TCPPARMS(TCPDATAT) >EZZ9298I GLOBALTCPIPDATA - None >EZZ9298I DEFAULTIPNODES - None >EZZ9298I GLOBALIPNODES - None >EZZ9304I COMMONSEARCH >EZZ9293I DISPLAY COMMAND PROCESSED > > >>If you use the DEFAULTTCPIPDATA statement, you do not need to have a >>SYSTCPD DD-statement in the TSO LOGON procedure used for the >>TSO "session" in which you enter the NSLOOKUP command. Maybe I'm >>misunderstanding something here. > >Chris, we have got it!!!!. Our SYSTCPD DD in our logon procedure was >allocating TCPDATA member (production member), not TCPDATAT. We have >changed in our logon procedure and it didnt' found the dns server. > >Thanks a lot!!! ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
