Mark This is the immensely complicated complete story as I worked it out for a query earlier this year. I hope it hasn't been made any more complicated in the meantime.
<quote> Base resolver configuration files --------------------------------- Resolver - GLOBALTCPIPDATA plus the first of the following% * Environment variable - RESOLVER_CONFIG * /etc/resolv.conf //SYSTCPD DD statement # x.TCPIP.DATA SYS1.TCPPARMS(TCPDATA) Resolver - DEFAULTTCPIPDATA TCPIP.TCPIP.DATA * only UNIX # x is userid for UNIX and userid/jobname/procname for MVS % If GLOBALTCPIPDATA used, the following are completely specified there: DomainOrigin/Domain NSInterAddr/NameServer NSPortAddr ResolverTimeOut ResolverUDPRetries ResolveVia Search SortList The following may also be found in the "search order" data set: ALWAYSWTO DATASETPREFIX HOSTNAME LOADDBCSTABLES LOOKUP MESSAGECASE OPTIONS SOCKDEBUG SOCKNOTESTSTOR SOCKTESTSTOR TCPIPJOBNAME TCPIPUSERID TRACE RESOLVER TRACE SOCKET </quote> This is an extract of the complete story on "Resolver search orders". "UNIX" applies to processes/programs which use the "UNIX environment" and, from your post, this "RECEIVE" function would appear to be one of those. "MVS" applies to processes/programs which use the "MVS environment". I can see two approaches. 1. Use "/etc/resolv.conf" in order to specify access to the name server system and verify with an onslookup command once in "UNIX" mode. 2. Go to the bother - probably worth it in the long term - of creating a RESOLVER cataloged procedure which identifies a file to contain the "resolver setup statements" which uses the GLOBALTCPIPDATA statement in order to identify a set of "resolver" or "TCPIP.DATA" statements, a file I used to teach as the "client data file", recalling that "client" in this case referred to all processes which relied on the main TCP/IP address space, whether logically, really "clients" such as TSO users, or "servers" such as, well, FTP. This is nearly all documented in Chapter 5, "TCPIP.DATA configuration statements" (1.5) of the z/OS V1R7.0 Communications Server IP Configuration Reference manual.The missing piece is the RESOLVER_PROC statement in the BPXPRMxx parmlib member. The RESOLVER_PROC statement in the BPXPRMxx parmlib member is covered in section 1.2.5.1, "Setting up a resolver address space" in the z/OS V1R7.0 Communications Server IP Configuration *Guide* manual - of all places. It may be useful to check out the whole 1.2.5, "Understanding resolvers" section. Because you can see a RESOLVER address space running, you may assume you must already have a RESOLVER started task procedure . This is not necessarily so. This is "smoke and mirrors" caused by subtle use of the IEESYSAS started task procedure (analyse what START IEESYSAS.RESOLVER,PROG=EZBREINI,SUB=MSTR means). I checked Pat O'Keefe's post and happily we are in agreement over the influence of GLOBALTCPIPDATA. We must have been reading the same manual. <g> Thanks for the explanation of why the SYSTCPD DD-statement doesn't work. That helps resolve (sic) the issues here. Chris Mason ----- Original Message ----- From: "Gibbons, Mark" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Monday, 30 October, 2006 8:22 PM Subject: Re: Receive Order Error > As far as I can tell. Internet retrieval creates and uses a unix process in another address space to retrieve orders. The systcpd dd statement is not passed to the new address space. The only method I've found that works is to have the data be found in the standard tcp search order. I'm not sure what the standard search order is (tcp config reference lookup a while back) but it will find: > > userid.TCPIP.DATA > SYS1.TCPPARMS(TCPDATA) > something in /etc/ > > IBM needs to let us specify this data for the receive. Much like they do the other information for client and orderserver. I'd be very happy if I was wrong however. We don't have our tcpd data in the standard search order. > > Mark ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
