There are a lot of FTP (QTFTPxxxxx) jobs starting and ending on one of my
systems.
We had this situation, but we caused it!
We don't run FTP at startup. So every time we need the FTP server, we have
to start it (and end it).
We have a job that transfers about 50 directories of information. It got
annoying having to babysit it because it broke so often. So, the job was
broken down into 50 separate sessions. We didn't understand the FTP client
versus server difference and bracketed the jobs with strtcpsvr *ftp and
endtcpsvr *ftp. This caused a large number of "abnormal completions" to
appear on one of our reports.
Does anyone have any suggestions?
I'd scan the source files for *ftp and see you have something similar going
on. If you don't find it in source, then you will need to catch them in the
act. Use an exit program or a SEP debug (as Rob suggested) to find out who
and what.
Mike Krebs
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Albert York
Sent: Monday, August 06, 2007 12:31 PM
To: Midrange tech forum
Subject: FTP jobs starting and stopping
There are a lot of FTP (QTFTPxxxxx) jobs starting and ending on one of my
systems. It seesm to be configured the same as the other systems. But on
those systems the FTP jobs start during the IPL and stay active.
Does anyone have any suggestions?
Thanks,
Albert
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.