Re: Another FTP question for the group

I should have provided more detail. We have the log for the FTP commands
going to a source physical file right now, so we can see what happens when
a failure occurs. So the printed report is superfluous. I just didn't
know if there was some sort of an option within FTP commands themselves
that causes the report to generate.

Bill

On Mon, Mar 28, 2016 at 11:36 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
wrote:

Something to think about.

If you turn off these logs, and you have a failure, you will not be able
to troubleshoot the failure.
The logs contain the details of the failure.
Think about a purge process that deletes the spoofile and/or IFS log more
than X days old.
We have both in place.

Also, normal FTPs OUTPUT append to the same member depending on the OVRDBF
location of OUTPUT.
Ours are all stored in QFTPSRC for each application.
You could add a CLRPFM of the OUTPUT prior to the FTP, thus keeping only
the latest FTP process.

/* FTP file to server */

OVRDBF FILE(INPUT) TOFILE(*LIBL/QFTPSRC) +
MBR(FTPBACPUTI) OVRSCOPE(*JOB) /* Input +
is keyboard */

Optional - CLRPFM FILE(QFTPSRC) MBR(FTPBACPUTO)

OVRDBF FILE(OUTPUT) TOFILE(*LIBL/QFTPSRC) +
MBR(FTPBACPUTO) OVRSCOPE(*JOB) /* Output +
is screen */

FTP RMTSYS('X.X.X.X')

Paul

-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Buck
Calabro
Sent: Monday, March 28, 2016 11:06 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Another FTP question for the group

On 3/28/2016 10:37 AM, Bill Howie wrote:

We have an automated FTP process that runs about every 10 minutes.
Currently this process generates a spool file of the log of the FTP
commands whenever the process is run. Is there a keyword somewhere
that will shut off the printing of these logs? As you might imagine,

with

running the process every 10 minutes these can tend to pile up. I can't
think of what it would be off the top of my head. Any info is as always
appreciated. Thanks!

The answer depends intimately on the nature of the process generating
them. Use WRKSPLF to find the job name that is generating these reports.
Armed with that, you can WRKJOB and find the call stack or job log, which
will tell you the name of the program generating them. Armed with that,
you can then investigate /why/ those logs are being generated and how to
stop them.

--
--buck

Visit wiki.midrange.com and register for an account. Edit a page that
helps you, and because it's public, you'll help someone else, too!

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.