Are you saying that DD SYSTCPD pointing to TCPIP.TCPIP.DATA or SYS1.TCPPARM fixes your problem? These datasets should be picked up without a SYSTCPD DD. I'm confused why you feel using these requires the resolver.
Jon Perryman. >________________________________ > From: Rob Schramm <[email protected]> >To: [email protected] >Sent: Monday, October 7, 2013 11:49 PM >Subject: Re: NSLOOKUP on MVS vs OMVS > > >Because that may or may not fix the issue. > >Setting up RESOLVER is not super hard. With the biggest benefit of never >coding SYSTCPD in a proc ever again!!! > >Rob Schramm >On Oct 7, 2013 5:24 PM, "Jon Perryman" <[email protected]> wrote: > >> Is there a reason you can't update TCPIP.TCPIP.DATA or SYS1.TCPPARMS with >> the change? >> >> Jon Perryman. >> >> >> >> >________________________________ >> > From: David G. Schlecht <[email protected]> >> > >> > >> >We have a solution, or at least a workaround. We'll continue to add >> SYSTCPD to every job that needs RESOLVER and will someday build an MVS proc >> for RESOLVER that can use GLOBALTCPDATA. >> > >> > >> >> ---------------------------------------------------------------------- >> 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 > > > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
