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

I want to make sure that it is simple to check
for these jobs and start if not running.

You could have your node.js process attempt an exclusive lock on a "known"
data area when it starts. If the data area is already locked, then
immediately end the Job.

Your "check" routine could also attempt an exclusive lock on the data area.
If it fails, that means your node.js process is running.

This technique of having servers lock a data area has been used for as long
as I can remember, something like 40 years.

Not to nit-pick on terminology, but it is confusing when you say that
"servers" are being "called" by other IBM i Jobs, when you really mean that
they are communicating via HTTP "requests" and "responses".