Carlos There was an aspect of your post which I hadn't fully resolved prior to my last post. I believe I may have appreciated what you may mean - while performing ablutions - a phenomenon of some antiquity as recorded in the case of Archimedes!
What I couldn't understand is the apparent presence of two sets of IP addresses, the 192.168.1.x set and the 201.56.7.x set. Perhaps the configuration you are struggling to describe involves a TELNET or TN3270 server involving somehow - perhaps - one of the sets of addresses - if so presumably the 201.56.7.x set - while you need to set up the whole of an instance of the IP component of z/OS Communications Server (CS) as a TELNET/TN3270 client for a single user using the 192.168.1.x set. This is an interesting task with which to be presented, namely, what is the minimum configuration required to operate z/OS CS IP as a something akin to a PC or UNIX workstation? Last month, I outlined my "rule of hand" for configuring a workstation. It was in a response concerning running SNMP on the HMC PC: <quote> The first thing you need to do is make sure that the HMC node is properly configured as an IP node. When I was having to set up "workstations"/"servers" for hands-on education purposes which I had to do for a dozen or so machines prior to every class, there were always 5 - the number of fingers on a hand! - elements to ensure were configured. It was particularly important that they were "ticked off" since this dated back to the days when OS/2 PCs had to be configured with line commands! - The node itself - (1) a name - The interface to the LAN - (2) an IP address and (3) a mask which when "anded" with the IP address defined an address range which should apply to the IP addresses of each interface connected to the same LAN, aka, the *subnet* mask, which enables the Address Resolution Protocol (ARP) and routing generally to operate correctly - Routing - (4) the IP address of the "adjacent" router interface which allows access to IP nodes other than those with interfaces directly connected to the same LAN - Name/address translation - (5) the IP address - often two for backup - of a server node which can translate names to IP addresses and IP addresses to names </quote> http://bama.ua.edu/cgi-bin/wa?A2=ind1106&L=ibm- main&T=0&F=&S=&P=154114 If you really want to reduce the work to a minimum, you can skip 1 and 5 which is significant in the this case where setting up the minimum seems to be desired - if not desirable. There is actually a default for 1 and, if you never actually bother with names and stick to numbers, you won't need a name server. In fact, I provided the answer to 2, 3 and 4 in my previous response. I'll now explain how. > HOME 192.168.1.230 LINKPROD > BEGINROUTES > ROUTE 192.168.1.224/28 = LINKPROD MTU 1500 > ROUTE DEFAULT 192.168.1.225 LINKPROD MTU 1500 > ENDROUTES 2 is the value of the HOME statement entry. I say "list entry" but there is only one "entry". I have also taken the opportunity to include a correction since I see I missed out the name of the LINK statement in the HOME statement list entry I posted before. 3 is specified by the value following the "/" in the first ROUTE statement. 4 is the IP address in the second ROUTE statement. If you wanted to specify your own name for your IP node, 1, you would need to define a generically named TCPIP.DATA data set and include a HOSTNAME statement. Even when creating a minimum configuration, you may find you need to set up this data set with statements such as DATASETPREFIX and TCPIPJOBNAME. Not wanting to get too complicated and taking notice that this is a minimal configuration with extraneous steps such as configuring VMCF/TNF thankfully avoided, I can say that the default value for the name of the IP node is the CVTSNAME, the SYSNAME value from the IEASYSxx parameter library member or the IEASYMxx parameter library member. If you want to benefit from the possibility to specify a name rather than an IP address in accessing servers such as TELNET and TN3270 servers, again you would need to define a generically named TCPIP.DATA data set and now minimally include an NSINTERADDR statement specifying the IP addresses of one or more name servers, 5. The NSPORTADDR, RESOLVERTIMEOUT, RESOLVEUDPRETRIES and RESOLVEVIA statements are related to use of the name server function but you could very probably to almost certainly survive using only the default values. > Since I´m not familiar to this, seems that all is defined in gateway statement. So, we've come a long way from the GATEWAY statement, both in time, since it should be replaced by the BEGINROUTES/ENDROUTES statement block using ROUTE statements, and in function, since rather more is required extending to rather more is desirable. Chris Mason On Fri, 1 Jul 2011 19:52:34 -0500, Chris Mason <[email protected]> wrote: >Carlos > >> I need to configure <something to do with the IP component of z/OS >Communications Server (CS)> > >> Since I´m not familiar to this, ... > >I suggest you get your colleague who *is* familiar with the IP component of >z/OS CS to subscribe to the IBMTCP-L list as recommended by Lizette Koehler >and post a much more accurately expressed specification of what you need >there. > >> My home address will 192.168.1.230, gateway is 192.168.1.225 and network >mask is 255.255.255.240 > >FWIW these specifications map to the following, assuming that LINKPROD is >the name of the LINK statement which is part of the definition of your >interface: > >HOME 192.168.1.230 > >BEGINROUTES > ROUTE 192.168.1.224/28 = LINKPROD MTU 1500 > ROUTE DEFAULT 192.168.1.225 LINKPROD MTU 1500 >ENDROUTES > >Note this is far more than "telnet access thru tcpip" but rather basic static >routing statements for any sort of traffic "out of" the CS IP node. > >Note further that, even if you cannot follow how I managed to create those >ROUTE statements - which is what you should be using these days rather >than the GATEWAY statement, your colleague who is familiar with the IP >component of z/OS CS will understand very well. > >Chris Mason > >On Fri, 1 Jul 2011 17:11:08 -0300, Carlos Bodra - Pessoal ><[email protected]> wrote: > >>Hello TCP/IP z/OS gurus >> >>I need to configure a telnet access thru tcpip z/OS 1.5. Since I´m not >>familiar to this, >>seems that all is defined in gateway statement. >> >>My home address will 192.168.1.230, gateway is 192.168.1.225 and network >>mask is 255.255.255.240 >>How should I define my gateway statement bellow: >> >>GATEWAY >>201.56.73.230 = LINKPROD 1500 HOST >>DEFAULTNET 201.56.73.224 LINKPROD 1500 0.0.0.8 201.56.73.0 >> >>Thanks in advance >> >>-- >>Carlos Bodra ---------------------------------------------------------------------- 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
