Just trying to figure out what you are asking.
At first I thought you wanted to know who was attaching to your IBM i by
accessing it at "myibmi" or whatever the name was and not by using the IP
address.
But as I thought about it perhaps you know you can do a NETSTAT *CNN but
you want to know who is access it by the end person's host name. IOW you
don't want to know that 10.10.4.27 is accessing your IBM i. You want to
know the host name of 10.10.4.27 so that if it is RALPHSPC you can talk to
Ralph and know that he will be affected.
I'm still trying to figure out why though. Because I don't think you can
determine if Ralph is accessing it by:
- using the IP address of your ibm i
- is using a host table entry on his pc.
- or is accessing it by using a dns entry from a dns server.
In theory you shouldn't care if they are using DNS. Sure they may be
affected. One little outage perhaps until the DNS cache is flushed and
they reconnect. We do a switch every quarter which involves a DNS change.
Works great. We quiesce the system before changing the DNS.
Now the ones you want to hunt down and kill are those using an IP address
or a local host table entry. Me, I figured it's their own stupidity and
forget them.
Now, there are some querying you can do
select
remote_address, remote_port, remote_port_name,
local_address, local_port, local_port_name,
myudfToDoaNslookup(remote_address)
FROM QSYS2.NETSTAT_INFO
https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20i%20Technology%20Updates/page/QSYS2.NETSTAT_INFO
Rob Berendt
midrange.com
