Re: Another FTP question for the group -- RPG400-L

Hi Roger

Just to add a thought - we use a basic script for FTP - just changing a sequential number in a file name each day. It used to override STDOUT or OUTPUT (I forget just now) to an OUTFILE that is copied to a history file.

We've started using Scott's FTPAPI, and it is really nice - every FTP subcommand has its own CL command, which has a return code and can get you the FTP error, if any.

I now write stuff to the job log, then retrieve whatever is in the job log for the process - using msg keys before and after and retrieving them all.

It'd be easy to add to that the kind of timestamp thing you describe.

Using the FTPAPI, we are able to halt the process in the event of a fatal error - like when you can't find the host address, of a directory cannot be changed to, etc.

This might not help you in the future, but maybe it'll be of use to someone reading the archives.

Will you be at COMMON this year? Gotta get that Dr Pepper - tastes best in the Southland!

Vern

On 3/28/2016 1:27 PM, Roger Harman wrote:

We have a number of old processes not migrated to GoAnywhere (yet... but they're on my hit list) that use this technique.

What I have been frustrated with is the inability to track date/time/job info. So, what I started doing was to add a header and trailer record to the output files using CL's RUNSQL. All these processes use a QTEMP copy of the file anyway and then copy it back to a production keeper.

RUNSQL <insert into ...... **START** date/time/job info>
<do the ftp process>
RUNSQL <insert into ...... **END** date/time/job info>
<copy/add the qtemp file to production>

Roger Harman
COMMON Certified Application Developer - ILE RPG on IBM i on Power

________________________________________
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxx> on behalf of Steinmetz, Paul <PSteinmetz@xxxxxxxxxx>
Sent: Monday, March 28, 2016 8:36 AM
To: 'rpg400-l@xxxxxxxxxxxx'
Subject: RE: Another FTP question for the group

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.