If it's a one time shot why write programs?
I find it much easier to write SQL for this kind of work. It's quick and
flexible.  
You can save your SQL statements into a source member and execute them as a
script using RUNSQLSTM later on if the need for this arises again.

Elvis

-----Original Message-----
 Subject: SQL Vs. RPG Opinions

I have a need to populate many files from an established iSeries
database. I would normally write some RPG/IV code to get the data I need
and write to the files - standard stuff. However, these files are going
to mimic a relational structure on a different system - after I create
the files, I'll convert them to comma delimited format and send them to
the target system where they'll be used as input for tables.

So, I'm really creating tables on my iSeries and sending them to the
other system. Should I use SQL to do this? I've used SQL to create the
tables and I could develop the SQL to populate the tables, but I'm
wondering if it even makes sense to do this. 

Thoughts?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.