If it's simply a csv why not just use CPYFRMIMPF?
From: "Jerry C. Adams" <midrange@xxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>,
Date: 11/15/2011 09:26 AM
Subject: RE: FTP Format
Sent by: midrange-l-bounces@xxxxxxxxxxxx
That's what I thought, David. They seem to love CSV (they use it a lot
for
other things). I have parsed CSV and other delimited files before, but
I'm
getting lazy in my old age (that's not true; I've always been lazy) and
having a relational bucket (i.e., table) for them to drop things in just
seemed a whole lot easier since I would have to add a front-end (parser)
to
the mix.
Jerry C. Adams
IBM i Programmer/Analyst
When A.G. Bell tried to sell his patent to Western Union, he was turned
down
with the words: "This electrical toy has far too many shortcomings to ever
be considered a practical means of communication." -EUI
--
A&K Wholesale
Murfreesboro, TN
615-867-5070
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Tuesday, November 15, 2011 9:04 AM
To: Midrange Systems Technical Discussion
Subject: Re: FTP Format
On 11/15/2011 8:58 AM, Jerry C. Adams wrote:
My question to the group is: Isn't FTP just a character-by-character
transmission? That is, the item number may be 1-5 numbers (1-99999).
If only '1' is transmitted, would not that mean that everything gets
PUT into the wrong locations of an SQL DDL file on our system in that
case?
The file that is transferred to the host would have to have some kind of
format ... it could be fixed format, csv, etc.
You just need to determine what the actual format is in order to parse it.
If it's fixed format, you won't have a lot to do.
david
midrange.com
