If you perform the following:
DSPLOG PERIOD((*AVAIL 112021)) MSGID(TCP2617)
You will see these messages.
If you press F1 on them you can see the local address (on your IBM i), the local port, the remote address and the remote port. Let's assume that the remote port is a meaningless random port so forget about that. Most of the local port entries I see are 8080. A sample being
- local IP address is 10.10.6.129
- local port is 8080
NETSTAT OPTION(*CNN)
F24=More keys
F15=Subset
Local internet address range:
Lower value . . . . . . . . 10.10.6.129
Upper value . . . . . . . . *ONLY
Local port range:
Lower value . . . . . . . . 8080
Upper value . . . . . . . . *ONLY
8=Display jobs
QP0ZSPWP, user MWIPROD. Here this is PTC's Implementer product. Our developers use it for change management.
On a Windows command prompt you can type in:
C:\Users\rob>nslookup 10.14.9.78
And it will tell you the name of the PC which connected. If you are a DHCP shop this can change. Most shops use DHCP for their individual client pc's IP addressing.
Or on the IBM i you can type in that NETSTAT *CNN again and subset it by that remote address and see if that person is connected again and what jobs they are using and that might give you their name. Providing it is the same person using the same dhcp assigned IP address.
By the way, all of this same information is available using SQL services:
DSPLOG:
https://www.ibm.com/docs/en/i/7.4?topic=services-history-log-info-table-function
NETSTAT *CNN:
https://www.ibm.com/docs/en/i/7.4?topic=services-netstat-info-view
NETSTAT *CNN, subset and show the jobs:
https://www.ibm.com/docs/en/i/7.4?topic=services-netstat-job-info-view
DSPUSRPRF to get the text of the user name:
https://www.ibm.com/docs/en/i/7.4?topic=services-user-info-view
NSLOOKUP is a command on the IBM i "IF" you have the following installed:
5770SS1 31 5050 Domain Name System
I only have that on limited lpars as it will get flagged as a security exposure because IBM i is always way behind on the bind release level.
I am sure that with the right YUM/RPM package installed there is an alternative.
I sure wish there was a sql service to perform the nslookup, and that it didn't require option 31 installed.
My rfe to break out the dns client nslookup from the dns server (and therefore not require 5770ss1-31) was rejected.
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.