RE: AW: SQL output to csv

Output to a csv is built into SEQUEL, and has been for lots of years.

Paul Nelson
Cell 708-670-6978
Office 409-267-4027
nelsonp@xxxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Wednesday, December 04, 2013 9:33 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: AW: SQL output to csv

These folks are getting a new time keeping system that they need to
initially populate with employee information which is the first
go-around on this. Eventually I'll need to make some modifications that
generate only changed records as a csv file. I might go with an RPG-SQL
solution in the long run. First pass is a one-off file (famous last
words: "We only need this once")

Pete Helgren
www.petesworkshop.com
GIAC Secure Software Programmer-Java

On 12/4/2013 9:21 AM, John Yeung wrote:

On Wed, Dec 4, 2013 at 9:54 AM, Pete Helgren <pete@xxxxxxxxxx> wrote:

RUNSQLSTM could be run after the file overrides are set but
again it would be at least a two stepper: Create the file and then copy
it to the IFS.

Depending on how many files/members you need to transfer, two steps
that don't require any additional tools or programming is not a lot of
steps.

It's not worth pulling out the big guns unless this is a big and/or
recurring task.

By the way, are the CSVs ultimately meant to be transported to some
other system, or are they meant to stay in the IFS? (Point being to
find out whether you can bypass generating CSVs in the IFS.)

John