× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Monitoring TCP/IP connections
  • From: "Kerwin Crawford" <crawfork@xxxxxxxxxxxxxxx>
  • Date: Thu, 17 Aug 2000 09:17:09 -0500

I would set up a never ending CL that would do a ping to the associated IP
Address.  If okay wait a few second then ping again.  If error send a
message out.

It sounds like it might be a lot of over head but my understanding is that
the ping is very low on overhead.  We did this and had the message go to
someone's pager.  It worked very good.  We usually knew we had a problem
before the person on the other end did.


==============================================
Kerwin S. Crawford
System Analyst
Toastmaster Inc.
A subsidiary of Salton, Inc.
==============================================

-----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
>+---

+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.