RE: FTP listener hung on port 21

I am assuming that " But it still has hold of Port 21" means that he is running NETSTAT *CNN to discover that the job still has a lock on port 21. Haven't really received a concrete confirmation of that.

A job in OUTQ may, or may not, have a joblog or a printed representation of the joblog. CLEANUP removes them after so many days.

And it is possible for a job to be ended and still come back alive and process data. Same job name, user and job number. Even across IPL's. It's quite common with the receiver jobs of SNDNETSPLF. Normally the only way to end those was with ENDJOB specifying to also delete all spool files. Then it would finally generate a new job under a new job number.

Also, keep in mind that WRKACTJOB has its own definition of an "active" job. Certain prestart jobs, etc which are very idle but not ended will no longer show up in WRKACTJOB. So the lack of appearance of the job in WRKACTJOB is no indication that the job has ended. I've seen this a lot.

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Troy Foster
Sent: Tuesday, April 30, 2019 4:45 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Subject: Re: FTP listener hung on port 21

If the job says outq, it means the job has ended and there is a job log.
Try doing wrkusrjob qtcp *active to see only the jobs that are still active.

On 4/30/2019 2:16 PM, Jack Woehr (jwoehr@xxxxxxxxxxxxxxxxxxxxxxxx) wrote:

On Tue, Apr 30, 2019 at 12:25 PM Rob Berendt <rob@xxxxxxxxx> wrote:

If NETSTAT *CNN does show the port still locked by this job and
ENDTCPSVR *FTP will not kill it then you could try ENDJOBABN.

Tried it. No luck. Have tried ENDTCPSVR *FTP, killing the job every
way I know how, WRKJOBLOG JOBLOGSTT(*PENDING) PERIOD((*AVAIL *BEGIN))
and killing it there, etc. etc. Now it says "OUTQ" in WRKUSRJOB.

QTFTP00184 QTCP BATCH OUTQ

But it still has hold of Port 21 and I can start and end *FTP without
changing that.

It finally produced a spooled file which tells me what I already know:
the job ended at 03:05 today abnormally. The immediately prior message is:

Cause . . . . . : Unexpected exit failure. The reason code is 1. The
reason
codes and their meanings follow: 1 -- Error in closing a process
descriptor.

DESPITE all this, it still owns port 21:

Display Jobs Using Connection
System:
Connection type . . . . . . : *TCP
Local address . . . . . . . : *
Local port . . . . . . . . . : 21
Remote address . . . . . . . : *
Remote port . . . . . . . . : *

Type options, press Enter.
5=Work with job

Current
Opt Name User Number Type User
QTFTP00184 QTCP 463564 *BCH

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: https://amazon.midrange.com