Howard, Unfortunately I'm not in a position to verify my suggestions.
Now I see that the name you need is not directly about making a TCP connection to another host, it's sort-of back to square 1. I rather think that the name you see on the in the header lines for messages from commands such as NETSTAT may be the procedure name. It may well be that the "hostname" is just that: the name following the HOSTNAME parameter of the TCPIP.DATA file for your system, also known as the "client data file". Ask your local specialist what the actual name of your TCPIP.DATA file is. One way to be sure you are displaying this parameter is to use the HOMETEST command. See section 1.5.5.6, "Verifying PROFILE.TCPIP and TCPIP.DATA using HOMETEST" in z/OS V1R7.0 Communications Server IP Configuration Guide. What you are doing looks like creating some keys for a security function or something like that. It would appear you are ensuring that the remote host is recognised by its name, specifically, referring to my earlier post, its "internal" name, the one identified on the HOSTNAME statement. You will be needing the HOSTNAME names of these remote ,"known" systems If that doesn't work, try using a fully qualified name, the sort that ends in .com or .net or .org or whatever. I guess you'll only know for certain when it all works. Chris Mason ----- Original Message ----- From: "Howard Rifkind" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Saturday, 18 March, 2006 10:31 PM Subject: Re: TCPIP Question > Well thanks everyone for trying to answer my question. I'm installing Ported Tools and I had been told to use the following command: > > You need to run a number of commands that you may want to build > into a script file. The commands will look like this > ssh-keygen -t rsa1 remote-hostname >> /etc/ssh/ssh_known_hosts > ssh-keygen -t dsa remote-hostname >> /etc/ssh/ssh_known_hosts > ssh-keygen -t rsa remote-hostname >> /etc/ssh/ssh_known_hosts > The remote-hostname is the TCPIP name of the remote system that > you will be connecting to. > > See remote-hostname above. > > The person who suggested NETSTAT HOME had a good thought and that command returned: > > EZZ2350I MVS TCP/IP NETSTAT CS V1R4 TCPIP Name: TCPIP 21:29:35 > EZZ2700I Home address list:, > EZZ2701I Address Link Flg, > EZZ2702I ------- ---- ---, > EZZ2703I 149.150.209.101 BUSTLINK P, > EZZ2703I 149.150.209.111 BUSTPLNK, > EZZ2703I 127.0.0.1 LOOPBACK, > > So I guess the TCPIP name is TCPIP. You got me. I'm a newbie in the USS business. > > > Charles Mills <[EMAIL PROTECTED]> wrote: > You want to have the tools talk to their own host system, the system they > are running on? The address of "me" is always 127.0.0.1 > > Charles > > > > -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf > Of Birger Heede > Sent: Saturday, March 18, 2006 7:35 AM > To: [email protected] > Subject: Re: TCPIP Question > > > Howard Rifkind wrote: > > 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: > From memory. > I think TSO command: NETSTAT HOME will tell you > > Birger Heede > IBM Software Group > > > > > > 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. ---------------------------------------------------------------------- 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
