Thanks for all the feedback. I'm having no luck. I've compared the TCPDATA member and the OMVS resolv.conf and see no meaningful difference between them. Still the MVS resolver is completely inoperative.
I'm inclined to open an SR with IBM and see if they can see what's different. Thanks, again, for your help. David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:[email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jon Perryman Sent: Tuesday, October 01, 2013 11:26 AM To: [email protected] Subject: Re: NSLOOKUP on MVS vs OMVS z/UNIX and z/OS have a different search order in locating the TCPIP.DATA that is used. In your case, you are maintaining 2 different files. Look at the IP Configuration Guide and search for TCPIP.DATA (I think). You should find a section that describes the search order. Jon Perryman. >________________________________ > From: David G. Schlecht <[email protected]> > > >Forgive me if this is obvious to everyone but me, but I’m seeing a difference >in the way name resolution (resolver) works on MVS and OMVS. In OMVS, a >command line ping or dig or nslookup all correctly resolve a domain name. >However, issuing the PING or NSLOOKUP command in TSO or PING in batch return >unknown host errors. > >I’ve tried adding the hostname to the /etc/hosts file but it changes nothing. > >Any idea why they’re different? Any idea on what I’m doing wrong? > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
