I forget the details, but when resolver is started without a proc, you get a "default". To provide the services you want, It will be necessary to provide a proc and customize.
See: IP Config. Guide. Chap. 14 - The Resolver http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/CCONTENTS?SHELF=f1a1bkd1&DN=SC31-8776-21&DT=20120119011927 And IP CONFIG Reference Chap 5 - Resolver setup and TCPIP.DATA configuration statements http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1B4B1/CCONTENTS?SHELF=f1a1bkd1&DN=SC31-8776-21&DT=20120119011927 HTH, <snip> 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? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
