Re: How to Take Snapshots of TCP/IP Connection Status info at

["Larry \"DrFranken\" Bolhuis" <midrange@xxxxxxxxxxxx>]

There is also an SQL service to capture this: QSYS2.NETSTAT_INFO

You can utilize that critter in SQL in any number of ways. Run it 
periodically as below adding to a table to collect historical 
connections is one option. Of course since it is SQL you can do things 
like select and omit, for example you may not want to clutter up your 
table with connections to and from 127.0.0.1 or omit listeners (Source 
and destination are both 0.0.0.0),  Additionally this guy has a TON of 
columns so you may wish to select only those which are interesting.

One note (A pet peeve of mine) if you Order By the IP address column it 
sorts the addresses as if they are alphabetic so you get address 
202.103... BEFORE address 47.44...

Sidebar: NewNav does NOT have this issue its netstat panel sorts 
correctly. :-)

I have even heard of this SQL somehow written (above my SQL pay grade) 
to ONLY add connections on local ports and addresses that have NOT 
already been logged to the table This keeps the table smaller and was 
used to identify who all is connecting to IBM i and who IBM i was 
connecting to.

	- DrF

On 9/16/2021 11:27 PM, kannan r wrote:
> Hi,
>
> If your system is having the latest QMGTOOLS library, there is a command NETSTAT2 in the library QMGTOOLS.
> This will dump the current NETSTAT connection details to a physical file.
>
> Only limitation is that the NETSTAT dump gets replaced every time even if we mention member option to *ADD in the command.
> To overcome the limitation you can copy the NETSTAT dump to another file.
>
> Sample PGM to collect the netstat for every 15 min:
>
> PGM
>
> LOOP: QMGTOOLS/NETSTAT2 OUTFILE(QGPL/NETSTAT)
> CPYF FROMFILE(QGPL/NETSTAT) TOFILE(QGPL/NETSTAT2) MBROPT(*ADD) FMTOPT(*MAP *DROP)
> DLYJOB(900)
> GOTO(LOOP)
>
> ENDPGM
>
>
> Thanks,
> Kannan.