Re: FTP Processing

[Jeff Young <jyoung0950@xxxxxxxxx>]

Daryl,
In this case, the target system is another (PC) server that runs a voice
picking WMS system.
We are sending updates and picking information to them via FTP.
The server is in the same physical location as the IBM i system.
I started this thread with the hope that there might be a way to determine
that all records I was sending were received, by sending one record at a
time.
One interesting thing that I found when reviewing the code in Scott
Klement's FTPAPI service program, is that in his send file routine, he gets
one record at a time and sends it to the target system.  While I could
clone that code and separate the read and write sections for my own
purposes, it is more work than I need to go to for this purpose.
I will just use normal FTP to send the data to the target system.

Jeff Young
Sr. Programmer Analyst

On Tue, Jul 21, 2015 at 8:05 PM, Darryl Freinkel <dhfreinkel@xxxxxxxxx>
wrote:

> Did I miss something ? What is the target system?
>
> In the past I put systems together to transmit files to third parties. FTP
> is used as it is an easy tool to implement but it has very little security
> in it. As such, an intermediary system is usually employed to receive or
> transmit data to. So you would send data to that system. Your third party
> would poll that system at their leisure and pull in the data. They would
> then run virus checks on the files and do validation processing.
>
> Using this process, you would not know if they had imported and updated
> the record into their system.
>
> Hopefully both side would include a header and maybe a trailer record
> providing account info, number of records and hash totals. Yes very old
> school but FTP is very basic. Your partner would validate the data on their
> end and if the hash totals etc fail, the file should be resent.
>
> You could send single record files using this process. If after a set
> amount of time, you don't get a resend request, you can safely assume the
> record processed safely.
>
> Darryl
>
> Sent from my iPad
>
> > On Jul 20, 2015, at 1:36 PM, rob@xxxxxxxxx wrote:
> >
> > What about any completion messages?
> >
> > DB2 file
> > put rob/deleteme rob/deleteme
> > 226 File transfer completed successfully.
> >    20 bytes transferred in 0.002 seconds. Transfer rate 10.240 KB/sec.
> > This 20 bytes refers only to the data space size.  Determined by the
> > CRTPF FILE(ROB/DELETEME) RCDLEN(10)
> > and the two rows I put into it.  Two ten byte rows equals 20 bytes.
> > Therefore it doesn't include the information displayed with DSPFFD or
> > DSPFD.
> > And I got 20 bytes if the file existed beforehand or not.  If it wasn't
> > created correctly beforehand I got a single row table (think pivot
> > table!).
> >
> > Stream file
> > put /rob/a.txt /rob/a.tst
> > ...
> > File transfer completed successfully.
> > 6 bytes transferred in 0.001 seconds. Transfer rate 6.144 KB/sec.
> >
> > Object . . . . . . :   /rob/a.txt
> > Size of object data in bytes . . . . . :   6
> >
> > Now script this:
> >
> > CRTPF QTEMP/FTPIN RCDLEN(100)
> > UPDDTA QTEMP/FTPIN
> >
> > DSPPFM QTEMP/FTPIN
> > ROB mypassword
> > BIN
> > PUT ROB/DELETEME ROB/DELETEME
> > QUIT
> >
> > CRTPF QTEMP/FTPOUT RCDLEN(100)
> > OVRDBF FILE(INPUT) TOFILE(QTEMP/FTPIN)
> > OVRDBF FILE(OUTPUT) TOFILE(QTEMP/FTPOUT)
> > FTP RMTSYS(mylpar)
> > DSPPFM QTEMP/FTPOUT
> > ...
> > 226 File transfer completed successfully.
> >    20 bytes transferred in 0.002 seconds. Transfer rate 10.240 KB/sec.
> > ...
> >
> > You may prefer FTPAPI over this but a lot of people use this technique.
> >
> > Rob Berendt
> > --
> > IBM Certified System Administrator - IBM i 6.1
> > Group Dekko
> > Dept 1600
> > Mail to:  2505 Dekko Drive
> >          Garrett, IN 46738
> > Ship to:  Dock 108
> >          6928N 400E
> >          Kendallville, IN 46755
> > http://www.dekko.com
> >
> > --
> > 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.
> --
> 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.