|
Thanks for your reply Vern
I was in fact thinking of doing that exact process
After all I know the number of fields involved and the size of each
resultant field
Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
Vern Hamberg
<vhamberg@comcast
.net> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
02/16/2010 05:05 Subject
PM Re: Parsing out a string
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Alan
This is what is known as CSV - comma-separated variable - something like
that. Can the fields also contain embedded full quotes? That's make it
harder.
I can think of a complicated way - write the string out to a stream file
in the IFS, then use the CPYFRMIMPF with parameters set with these
delimiters, and it'll arrive in a PF.
Or if you know the length is never longer than some value, write it to a
single-column PF (not DDS-based, use record length on CRTPF) first, then
use CPYTOSTMF to get it to a stream file, than do the CPYFRMIMPF.
This takes heavy lifting out of it. I didn't say it was pretty!!! But
you'd get it written quickly. Figuring out a CSV parsing routine - well,
there are probably examples in C or whatever out there. Google for csv
and parser
HTH
Vern
Alan Shore wrote:
Afternoon everyonewill
I am to receive a string that contains a number (9) of fields that are
comma separated.
Each of these fields COULD also contain commas, therefore these fields
be incased in double quotes (")--
Is there anything in SQL and/or RPGILE that will parse this data into
individual fields or is it a case of building my own logic
I've just re-read this e-mail and it looks familiar
I'll check the archives as well
Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.