×
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.
Rob,
If you check DSPLOG at the same time of the connection, do you see any new jobs staring/ending?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob Berendt
Sent: Thursday, February 25, 2016 9:50 AM
To: Midrange Systems Technical Discussion
Subject: Re: [Bulk] Re: What job is trying to communicate out via a certain port?
Not open long enough to catch it. They open/close their port really fast.
Subsecond.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Mark S Waterbury <mark.s.waterbury@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 02/25/2016 09:44 AM
Subject: Re: [Bulk] Re: What job is trying to communicate out via a
certain port?
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Rob:
What about NETSTAT option 3, then you can type an "8" next to the port
in question to see what job(s) are using that port?
HTH,
Mark S. Waterbury
On 2/25/2016 9:02 AM, Rob Berendt wrote:
TRCCNN contains no job information
TRCTCPAPP *DIRSRV only traces the server job QUSRDIR. I'll try it on
the
target but I seriously doubt it will tell me what job on the client is
trying to connect.
Rob Berendt
midrange.com
