Richard, If you use a customized "resolver", you can, apparently, add yet another layer of complication to an already convoluted process in the matter of determining the source of the following two sets of information:
- base resolver configuration file otherwise known as the "client data file" or TCPIP.DATA - local host table But, as you said, by using a customized "resolver", you may achieve overall simplification. The data set you identify using the SETUP DD statement in your customized "resolver" procedure[1] can supply up to 5 statements.[2] [1] In the example you supplied this is the SYS1.PARMLIB(RESSETUP) data set. [2] Strictly there are 6 but one, NOCOMMONSEARCH, is default and I can see no reason ever to specify it. If you specify a name for a "local host table" in the GLOBALIPNODES statement *and* you also include the COMMONSEARCH statement, you indeed provide an universal "local host table". If the COMMONSEARCH statement is *not* included, only IPv6 address in your "local host table" will be used. If you specify a name for a "local host table" in the DEFAULTIPNODES statement, you provide a default[3] "local host table" for IPv6 addresses and, if you also include the COMMONSEARCH statement, also for IPv4 addresses. [3] Rather oddly, it's not the "default" of last resort since, even if DEFAULTIPNODES is not specified, /etc/ipnodes will be used. If you have specified COMMONSEARCH[4], the alternatives you can have which lie between the data set defined by GLOBALIPNODES and the data set defined by DEFAULTIPNODES are, in "search order" order, the following: o Environment variable - RESOLVER_IPNODES - if your environment is "z/OS UNIX" o userid.ETC.IPNODES - where userid can be jobname or procname if your environment is "MVS" o hlq.ETC.IPNODES Note that in all cases with COMMONSEARCH[4], your "local hosts table" is in the simple UNIX format - I was going to add "colon-free" but then I recalled how IPv6 addresses are represented. <g> Thus if you want to use an universal "local host table" in the UNIX format you can specify the name in GLOBALIPNODES and specify also COMMONSEARCH[4]. If you previously had a number of "private" x.HOSTS.xxxxINFO files, maybe even duplicated sets, you have achieved simplification. [4] I am addressing this topic assuming you have only IPv4 addresses. If you have IPv6 addresses, the "search order" I have described here is always used. As for understanding fully the data set identified by the SETUP DD statement, there are the other two statements: GLOBALTCPIPDATA and DEFAULTTCPIPDATA. If you want to provide an universal "client data file" for your "client"[5] address spaces, you can specify the GLOBALTCPIPDATA statement. You should be sure to specify all the parameters you need and probably - in case your installation has been "messy" regarding the specification of "client data files" - you should not rely on defaults. The reason for this is that, for a subset of statements, the "resolver" will go looking for another "client data file" in the "search order" for any missing statement. [5] Where "client" program here means a program which relies on the main CS IP address space and, at the very least, has to know where it is, hence the TCPIPJOBNAME statement in the "client data file". I expect some installation might find a use for the DEFAULTTCPIPDATA statement. I can't think of one for the moment. Chris Mason ----- Original Message ----- From: "Richard Pinion" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Friday, 12 May, 2006 6:18 PM Subject: Re: Revolver Issue > Maybe I don't understand the RESSETUP. But I thought, depending on what I have coded, that is the place and order of search???? I don't have to guess or trace. > > >>> [EMAIL PROTECTED] 5/12/2006 12:09:54 PM >>> > Richard, > > I'm not quite sure what you mean here. Presumably you have specified the > "resolver" statements you want in the RESSETUP member and this takes you > into the maze of specifications from which it seems folk need the resolver > trace in order to be extracted. > > Chris Mason > > ----- Original Message ----- > From: "Richard Pinion" <[EMAIL PROTECTED]> > Newsgroups: bit.listserv.ibm-main > To: <[email protected]> > Sent: Thursday, 11 May, 2006 8:01 PM > Subject: Re: Revolver Issue > > > > Doesn't the RESOLVER address space setup the default resolver > configuration? > > > > ISREDDE2 SYS1.PROCLIB(RESOLVER) - 01.02 Columns > 00001 00080 > > Command ===> > Scroll ===> CSR > > ****** ********************************* Top of Data > ********************************** > > 000001 //RESOLVER PROC PARMS='CTRACE(CTIRES00)' > > 000002 //* > > - - - - - - - - - - - - - - - - - - - - - - 5 Line(s) > not Displayed > > 000008 //* > > 000009 //* Function: Start Resolver > > 000010 //* > > 000011 //RESOLVER EXEC PGM=EZBREINI,REGION=0M,TIME=1440,PARM=&PARMS > > 000012 //* > > - - - - - - - - - - - - - - - - - - - - - 20 Line(s) > not Displayed > > 000033 //SETUP DD DSN=SYS1.PARMLIB(RESSETUP),DISP=SHR,FREE=CLOSE ---------------------------------------------------------------------- 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
