RE: Best way to monitor for Running Node server on IBM i

OK, so I just tried this to check what jobs have a port in use:

// Looks like the same info you get from NETSTAT. Gives a job number that holds a port
SELECT * FROM QSYS2.NETSTAT_JOB_INFO WHERE CONNECTION_TYPE = 'IPV4'
AND LOCAL_PORT IN (1080)

This looks promising at least for web daemons anyway.

Here's an article from 2016 :
Surge Of Services In DB2 For i, Part 1
https://www.itjungle.com/2016/04/05/fhg040516-story01/

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------

message: 1
date: Fri, 28 Feb 2020 18:11:40 +0000
from: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
subject: RE: Best way to monitor for Running Node server on IBM i

On a similar vein, I had a thought recently that goes like this. Run a watch over CPF1240 (Job &3/&2/&1 ended abnormally) and interrogate the job name.

So far, it's just a scribble on a piece of paper.