Re: FTP Processing

Thanks Rob.
The temporary file will most likely be my solution.
The purpose of sending individual records was that if there was a
transmission problem that aborted the FTP session, I would know exactly
which records had been sent so that I could just resend the balance.

Jeff Young
Sr. Programmer Analyst

On Mon, Jul 20, 2015 at 10:43 AM, <rob@xxxxxxxxx> wrote:

In B2B data exchange one could use the standards, like ANSI X.12 or
EDIFACT, or at least use the basic concepts. For example, in EDI I'll
send some data to a trading partner (customer or vendor) and they'll send
me back a 997 that they have received it.
For more detail there's this exchange: I could send a PO and they could
send me back a PO Acknowledgement.

Is their FTP even capable of handling appending, or frequent updates?
Let's look at how this may be done.
Someone FTPs data to me.
First I either check for the data on a periodic basis to see if the file
exists or have some way of knowing that a new file has appeared.
Then I check for a lock on that file so that I know that they are done
transmitting. (which, if you are doing "row at a time" can be tricky)
I may, or may not, check for the presence of another file indicating "I am
done, you can process what I've sent you".
Then I post that data into my ERP system.

So, if you start doing row at a time updates to this business partner are
you going to bugger up their system?

This logging you are attempting to do almost sounds like there is some
dispute going on between you and this partner as to whether or not you've
sent the data. If you're already in the dispute stage then changing this
to a row at a time isn't going to resolve it.

If a dispute is not the case, and you're simply trying to track what
you're sending out via FTP then write the new rows to a temp file. FTP
them over as one transmission. When the session is complete, then update
the table that the subset has been transmitted.

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





From: Jeff Young <jyoung0950@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 07/20/2015 10:22 AM
Subject: Re: FTP Processing
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Thanks Rob, but this needs to be FTP.
That is required by the company we are sending data to.

The number of transactions is most likely to be very small as we are only
sending updates to selected master files which does not happen often.

Jeff Young
Sr. Programmer Analyst

On Mon, Jul 20, 2015 at 10:20 AM, <rob@xxxxxxxxx> wrote:

Back in the stone age we used to use something called a "DDM file" DDM

=

Distributed Data Management
CRTDDMF FILE(LOCALLIB/LOCALFILE) RMTFILE(REMOTELIB/REMOTEFILE)
RMTLOCNAME(myibmi *IP)

The advantage to the other way is, with the right drivers, you can hook

to

other databases. See ARDGATE for example.


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.



--
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.