David, Check your TCPIP.PROFILE. Do you have a GLOBALTCPIPDATA or DEFAULTTCPIPDATA in your profile? Either of these statements will modify the search order.
Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of David G. Schlecht Sent: Thursday, October 03, 2013 1:10 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NSLOOKUP on MVS vs OMVS Not having much luck with the SR. Might be a communications issue. Can anyone help? We have RESOLVER started in OMVS. There is no MVS proc for starting RESOLVER. We specify SYSTCPD in our TCPPROC JCL. From my read of the docs, SYSTCPD is found in the search order. Still, RESOLVER doesn't find it. RESOLVER fails in MVS. If I specify SYSTCPD in EVERY ONE of my MVS jobs that uses RESOLVER, it mostly works. This is not an acceptable solution as this means changing every job when the location of SYSTCPD changes. Furthermore, according to the documents, this should only be needed when you have more than one IP stack. The crux of the problem is that Websphere, which also has the SYSTCPD hard coded, is still unable to get resolver to work. The solution seems to be to find out how to get resolver to use the SYSTCPD provided to TCPPROC. If this isn't reasonable, is there any way to get a global SYSTCPD to work without building an MVS proc for RESOLVER? David G. Schlecht | Information Technology Professional State of Nevada | Department of Administration | Enterprise IT Services T:(775)684-4328 | F: (775) 684‐4324 | E:dschle...@admin.nv.gov -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Rob Schramm Sent: Wednesday, October 02, 2013 7:49 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: NSLOOKUP on MVS vs OMVS The documented ways that name resolution work and the order of evaluation is in the "IP Configuration Guide" "Chapter 10. The Resolver" section "Resolver configuration files" sub-section "Search orders used in the z/OS UNIX environment" and "Search orders used in the native MVS environment" Of course if you configure RESOLVER and just use COMMONSEARCH, then there is only one way Unix and MVS accomplish search order... which IMHO is far superior and easier to diagnose where problems are. Rob Schramm Rob Schramm Senior Systems Consultant Imperium Group On Tue, Oct 1, 2013 at 3:45 PM, David G. Schlecht <dschle...@admin.nv.gov>wrote: > 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:dschle...@admin.nv.gov > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] > On Behalf Of Jon Perryman > Sent: Tuesday, October 01, 2013 11:26 AM > To: IBM-MAIN@LISTSERV.UA.EDU > 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 <dschle...@admin.nv.gov> > > > > > >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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
