Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Monitoring TCP/IP connection

217 views
Skip to first unread message

oliver...@my-deja.com

unread,
Aug 17, 2000, 3:00:00 AM8/17/00
to
Hello,

we have an AS/400 620 running V4R3 and two
Unix-boxes (RS/6000)
accessing AS/400 files via TCP/IP and DB2-Connect.

I can see several jobs (QRWTSRVR) running in
QSYSWRK and some
connections in netstat using port drda.

We want to automatically monitor these connections
- i.e. we want
to know asap when traffic stops.

Are there any API's or other possibilities to
check traffic (beyond
ping)?

Thanx,

Oliver


Sent via Deja.com http://www.deja.com/
Before you buy.

Karl Hanson

unread,
Aug 17, 2000, 3:00:00 AM8/17/00
to
oliver...@my-deja.com wrote:
>
> we have an AS/400 620 running V4R3 and two
> Unix-boxes (RS/6000)
> accessing AS/400 files via TCP/IP and DB2-Connect.
>
> I can see several jobs (QRWTSRVR) running in
> QSYSWRK and some
> connections in netstat using port drda.
>
> We want to automatically monitor these connections
> - i.e. we want
> to know asap when traffic stops.
>
> Are there any API's or other possibilities to
> check traffic (beyond
> ping)?
>

One thing you could check into on the AS/400 side is the TCP/IP
attribute TCPKEEPALV (keep alive), eg on CHGTCPA command. This
specifies a time between probes over a socket connection. I don't know
the details, or even if this would help, but here are some pointers to
documentation:

TCP/IP Config & Reference:
http://publib.boulder.ibm.com:80/cgi-bin/bookmgr/DOCNUM/SC41-5420-03

Sockets APIs:
http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/info/apis/unix8.htm

Sockets Programming:
http://publib.boulder.ibm.com/pubs/html/as400/v4r5/ic2924/info/rzab6mst_frm.htm

--

Karl Hanson

shaha...@yahoo.com

unread,
Aug 18, 2000, 3:00:00 AM8/18/00
to

> One thing you could check into on the AS/400 side is the TCP/IP
> attribute TCPKEEPALV (keep alive), eg on CHGTCPA command. This
> specifies a time between probes over a socket connection.

Keepalive will not serve the poster purpose. It will just "sense" that
the unix side of the socket is dead and will accordingly kill the
socket on the as400.

Surprisingly i could not find anything formal and i end up with writing
a tiny utilty to retrieve a Specified port status. Then i use this
utility in order to shout when the socket is not listening.

I you need the utility send me an email,

Regards

0 new messages