Rogers, I'm glad you've managed to get it working.
Unfortunately, you haven't said enough about what you have done to get it working. SYS1.TCPPARMS is a partitioned data set where very many parameter data sets may be tidied away as members. The data set name is very commonly given in examples throughout the CS IP Configuration Reference manual. Of course, if a data set is referenced by means of a JCL DD statement, any name can be chosen. CS IP, however, true to its VM roots, does like to allocate data sets by name. SYS1.TCPPARMS(x) is so allocated for a number of "server" address spaces as follows: SYS1.TCPPARMS(FTPDATA) SYS1.TCPPARMS(OSNMPD) SYS1.TCPPARMS(PWSRC) SYS1.TCPPARMS(SNMPTRAP) In addition SYS1.TCPPARMS(TCPDATA) is one of the ways that the generic TCPIP.DATA data set, otherwise called the "client data file", may be identified. The only way I can see SYS1.TCPPARMS being involved in providing the "local host table" is by means of the member TCPDATA containing the DATASETPREFIX statement identifying your x.HOSTS.ADDRINFO and x.HOSTS.SITEINFO data sets by specifying "x". I guess you were not relying on the default, TCPIP as a high level qualifier for any other dynamic allocation. Unfortunately in my past playing with CS IP - nearly always using test systems, I have never needed to use the "resolver trace" function to help me out which is clearly my loss. I used to rely on students to make mistakes that I needed to sort out but my TCP/IP for MVS class module exercises were never sufficiently "unstructured". Regarding "changing the default", I now have to assume you are referring to TCPIP.DATA. As I have deduced - possibly erroneously - above, you are using SYS1.TCPPARMS(TCPDATA) and you would prefer something other way to specify the DATASETPREFIX and, possibly, other statements, for example, the statements which would allow you to use a name server. The possibilities are as follows, in the "search order": Environment variable - RESOLVER_CONFIG /etc/resolv.conf //SYSTCPD DD statement userid/procname/jobname.TCPIP.DATA SYS1.TCPPARMS(TCPDATA) Resolver - DEFAULTTCPIPDATA TCPIP.TCPIP.DATA The first two are available only when the address space program corresponds to the "z/OS UNIX" environment as opposed to the "MVS" environment. If you look in section 1.2.8.2.1, "Search orders used in the z/OS UNIX environment" of the CS IP Configuration Guide, you'll see how you can specify the data set name using the RESOLVER_CONFIG "environment variable" and there's even a clever format which allows use of a DD statement rather than a dynamic allocation. /etc/resolv.conf is one of those HFS files. With the SYSTCPD DD statement, you get to select the name of your data set in the most straightforward way. userid/procname/jobname.TCPIP.DATA is rather similar to the way that the HOSTS.xxxxINFO files are allocated. I've cheated a little here since, in the "z/OS UNIX" environment, only "userid" applies whereas in the "MVS" environment, it depends on whether or not the address space is a TSO user: userid, a started task: procname, or a job: jobname[1]. SYS1.TCPPARMS(TCPDATA) you know about - I think. In order to use the DEFAULTTCPIPDATA statement, you will need to provide a customized "resolver" procedure similar to the one posted by Richard Pinion. The way you tell MVS/UNIX System Services that you want this procedure to be used rather than the default IEESYSAS PROG=EZBREINI is to change the RESOLVER_PROC(DEFAULT) statement in SYS1.PARMLIB member BPXPRMxx to RESOLVER_PROC(<your-procedure-name>), it being conventional and sensible, although not mandatory, to keep the name RESOLVER for the procedure name. Having set up your own "resolver" procedure, you can then include the DEFAULTTCPIPDATA statement in the SETUP file naming the TCPIP.DATA file to be dynamically allocated. Lastly, you can just specify the TCPIP.DATA parameters in the file TCPIP.TCPIP.DATA to have the minimum flexibility but the maximum predictability. If you have gone to all the trouble of setting up the "resolver" procedure, you might like to simplify the specification of the "local host table" by including the DEFAULTIPNODES statement naming a file using the usual UNIX/Windows (and Linux, I guess) format for associating IP names and addresses in place of the old RFC 952 format. You also have to specify the COMMONSEARCH statement which is a rather roundabout way of consigning the old x.HOSTS.xxxxINFO data sets to the realms of not particularly fond memory. Have we finished with this TCPIP.DATA data set? Well, not completely. Although you may not need this information right now, it's as well to know in case you are sharing these specifications with a colleague or two and he/she knows that there is also a GLOBALTCPIPDATA statement (and a GLOBALIPNODES statement) and is tempted to use it. The point of which to be aware is that a subset of parameters, characterised by being associated with the invocation of name servers, is always taken from the GLOBALTCPIPDATA data set and the remainder are taken from whichever TCPIP.DATA data set is found in the search order I gave above.[2] There's still one issue outstanding which is whether or not the environment of your batch FTP address space is "z/OS UNIX" or "MVS". I don't know; the manual is not at all clear on the matter. I'm going to take this up in a response to one of Pat O'Keefe's posts. This matters only if you want to try to use the "environment variable" technique to specify the TCPIP.DATA data set or to use /etc/resolv.conf. [1] This was something I got confused in my last post to you where I suggested you could use "userid" in a job or started task. Multiple readings of the relevant sections of the manual have convinced me CS IP takes a simpler approach than I have described here - for the "MVS" environment. In the "z/OS UNIX" environment - which may well apply to your case - only the "userid" applies. [2] That's also for the clever folk who scan my list above and wish to point out I've missed something.<g> Chris Mason ----- Original Message ----- From: "Laine, Rogers" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 11 May, 2006 7:53 PM Subject: Re: Revolver Issue > What I found in the revolver trace is it was using SYS1.TCPPARMS as the > default, so I made my changes there and it now works. > My next question is where can I change this default to something else? > > Rogers ---------------------------------------------------------------------- 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
