FTPAPI is great but I believe it's not secure enabled; we need secure connections in most of our FTP process outside the company. More and more our vendors are asking for SFTP file transfer.
We use two methods. FTP2 from TAATOOLs or SFTP from GOANYWHERE Managed File Transfer. If you need SSH FTP capabilities this GA is really great. We have had one small problem with using GA in that sometimes our replication product starts journaling an IFS location and causes GA to return a 3474 error code. We have gotten this fixed to a point by turning off journaling on the IFS locations we use with GA (as from our point of view) they are just work file locations.
We put together a database system based on the command interface of FTP2 and recorded all the actions, connections and logins for anything we wanted to FTP. We wrote a command interface that allows us to just name the FTP project and have it execute all the FTP steps needs. We even have retry features and TEST system checking just so we don't send electronic payments to the banks, etc. Our FTP command interface allows for overrides to some of the parameters from the outside so you can have things like variable file names to send.
After we installed GA a programmer here wrote GA projects to give a fine grain control over SFTP command steps (Linoma GA did not have that detailed of SFTP features when we bought it). We then incorporated the details of these GA projects into our FTP database system. So with the same FTP command of ours we can run FTP2 scripts or GA SFTP scripts (or initiate PGP encryption). We can even set up variables that get passed into the GA SFTP project that come from out FTP command interface.
GA has a RUNPROJECT command and API's that are really flexible. One down side to storing FTP scripts this way is we use Hawkeye for cross reference and we have to build the cross reference data if we want to know anything about data objects being used.
Thanks, Matt
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Michael Ryan
Sent: Wednesday, March 23, 2016 11:43 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: Dynamic FTP script creation
Use FTPAPI instead of an FTP script. Then it's just a program and can be driven by whatever parameters you wish.
https://www.scottklement.com/ftpapi/
On Wed, Mar 23, 2016 at 1:41 PM, Bill Howie <blhowie66@xxxxxxxxx> wrote:
Hello all,
Question for the group.....I'm looking at various methods for dynamic
FTP script creation. I have an option where I just create a physical
file with one long field and then put my FTP commands in there. We
have another example where we put the commands in an array within an
RPG program and then read the array to build the command file. Both of
these require typing all of the commands somewhere, whether in a file
or a program. Anyone out there have a whiz-bang, gee-whiz approach to
this that is a lot slicker in how it sets up the commands? I know to
an extent we always have to manually do some part of it to have file
names, etc. be right. But I'm wondering if there's a better way to enter the "generic" commands
themselves? Hoping I'm making sense here. All input appreciated.
Thanks!
Bill Howie
--
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.
midrange.com
