Re: Monitoring TCP/IP connections

[John Hall <jhall@xxxxxxxxxxx>]

We use messenger plus from bytware to monitor our server jobs.  It
basically calls the API's to do a wrkactjob and can monitor just about
anything about any active job.  It can also do a "ping" but this doesn't
tell you much.  What are the symptoms when the jobs stop working?  Do
they disappear or go to MSGW or LCKW on the 400?  

If there is no clear way to tell when the job has stopped processing
consider a trigger on the file that   updates a data area with a time
stamp every time the file is updated by one of those jobs.  Then you
could use a CL to monitor the data area and if the transactions stop you
will know about it.

You might even consider setting up a dataq write to it from the trigger
program.  Do a timed read from the CL.  If the read times out the
transactions have stopped

John Hall
Home Sales Co.


> -----Original Message-----
> From: oliver.wenzel@cibavision.Novartis.com
> <oliver.wenzel@cibavision.Novartis.com>
> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com>
> Date: Thursday, August 17, 2000 5:30 AM
> Subject: Monitoring TCP/IP connections
> 
> >> Hello,
> >>
> >> we have 2 Unix boxes (RS/6000) accessing our 620 (V4R3) via TCP/IP and
> >> DB2/Connect. We need some automatic means
> >> of monitoring these connections - i.e. we want to know asap when
> >> transactions cease or stop.
> >>
> >> The Unix boxes constantly read/update about 5 files on the AS/400. There
> >> are five jobs running in QSYSWRK called QRWTSRVR
> >> and 5 connections in netstat (option 3) under port drda.
> >>
> >> Are there any other possibilities to check for activity for these two
> >> boxes - beyond wrkactjob/netstat?
> >>
> >> Thanx,
> >>
> >> Oliver
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---