Re: What job is trying to communicate out via a certain port?

I have two lpars in this thread: GDISYS1, GDISYS2
On GDISYS1 I do WRKJOB QUSRDIR and look at the joblog and I see:
Message ID . . . . . . : GLD0120
Message . . . . : Bind error with directory server.
Cause . . . . . : Distinguished name (dn) 'CN=ADMINISTRATOR' at IP
address
10.10.6.129 failed to bind with the directory server.

The IP address for GDISYS1 is 10.17.6.129 and the IP address for GDISYS2
is 10.10.6.129.
I can run a comm trace on both lpars and I can see that port 389 on
GDISYS1 address 10.17.6.129 is being accessed from port 42408 from address
10.10.6.129 from GDISYS2.

I'm trying to determine what job is trying to perform an ldap bind from
GDISYS2 onto GDISYS1 using the name CN=ADMINISTRATOR.

Comm trace does not display jobs on either the source or target side.

NETSTAT *CNN requires that I am constantly refreshing it and I've been
unable to catch it. It doesn't have an output option to put it into a
program loop. Like the following:
create table rob.netstatstuff as (
select current timestamp as TS, n.*
from qsys2.netstat_job_info n
where n.local_port=42408
) with data

// start loop
insert into rob.netstatstuff (
select current timestamp as TS, n.*
from qsys2.netstat_job_info n
where n.local_port=42408
)
// end loop

Again, you're timing has to be perfect otherwise you get:
SQL0100 - Row not found for INSERT.

Is there a better way to determine who is trying to bind via ldap?


Rob Berendt