Howard, It's the weekend so I'll try to help in the probable absence of more knowledgeable contributors.
It might have been useful to identify precisely which tool it was you were trying to install. If this is really a matter of connecting your IP node (z/OS system) to some other IP node, then you probably simply need to know the IP address of the other IP node, more precisely, the IP address of a reachable interface[1] on he other IP node. If the "tool" mentions "name" it presumably expects to be able to convert the name to a suitable IP address, possibly more than one, using a name server. I think I can fairly say all[2] IP programs will take either an IP address or a name as the identification of an IP destination. So, for "the remote system that you will be connecting to" using the tool you are installing, presumably you have either an IP address or a name. You can very probably use either. Your own system has its own name. This is the name you place in the TCPIP. DATA data set after the HOSTNAME statement. However the name specified in TCPIP.DATA stays internal to your z/OS IP node. External IP nodes know a name associated with your z/OS IP node only if it forms part of a name server record which supplies the IP address of one or more (logical) interfaces on your z/OS IP node. It's conventional - and aids sanity - that the internal name and the external name are the same. There is an alternative to the name server in that the name to address association could be from an "etc/hosts" file, or the equivalent, on the external IP node. And it seemed such a simple question. :-) Incidentally your post appeared twice - well, it's better than not at all which sometimes happens to some of mine. Chris Mason [1] Of course, the IP address may be of a logical interface such as a VIPA which represents the IP node itself or one of the service applications running on the IP node. [2] Probably the only exceptions are little test programs you can find as samples which actually risk encouraging bad habits. A well-written program will try to convert the destination parameter as a possibly "dotted decimal" number into a 4-byte[3] IP address. If this fails, the parameter is assumed to be a name and the name server is called with gethostbyname(). Gethostbyname() returns a structure which can contain a list of IP addresses. If the protocol to be used is TCP, a well-written program will try each of the IP addresses in turn in a connect() call . (I expect a program using UDP could build something equivalent into its logic.) [3] I expect the inet_addr() call can now somehow cater for IPv6 addresses. ----- Original Message ----- From: "Howard Rifkind" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Saturday, 18 March, 2006 4:01 PM Subject: TCPIP Question > I receive the following message and I'm installing Ported Tools but I need to know how to fine the host name they are talking about: > > The remote-hostname is the TCPIP name of the remote system that > you will be connecting to. > > Where would I fine the host name used in TCPIP use by my z/OS system. > > Thanks. ---------------------------------------------------------------------- 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
