Re: Making the most, or over-thinking it - SQL for uploads

"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 08/30/2016 12:15:12 PM:

----- Message from Duane Scott <dscott@xxxxxxxxxxx> on Tue, 30 Aug
2016 16:03:43 +0000 -----

To:

"Rational Developer for IBM i / Websphere Development Studio Client
for System i & iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Making the most, or over-thinking it - SQL for uploads

Thanks for the responses.

Vern - Not necessarily a one-time task as importing data from PC to
DB2 is done constantly, and there are many ways to do so. However,
using SQL is my FIRST thought over most of the tools that we have
access to, simply because of its convenience. At least perceived
convenience. As to the method that I used to get the data this
time, I used Access Client Solutions Data Transfer. But doing so
forced me to load the entire record to a DB2 data file from which I
used interactive SQL from an IBM i ACS emulation session to INSERT
my selected fields. Note: my first transfer using ACS was not
exactly easy until I figured out how different it was from the old
Client Access. But I endured and achieved the success I needed to
"get 'er done".

Buck - I figured as much since I couldn't find much in the way of
assistance through Google or WDSCI-L. But I wasn't sure I had used
the correct terminology in my search. I am fairly certain that I
have access to MySQL or SQL server, because I've toyed with it on
non-IBM i projects. Very briefly. And the files I used were
already structured for use with the access. But I'm not familiar
with setting up the PC to interact. Thus the request for a primer,
which was basically a shot in the dark. I think I understand what
you are saying about it being a part of a MySQL schema already set
up, which it is not.

I really just figured that I could access text files similar to
accessing them as done on IBM i. I also figured that it was my own
lack of experience and knowledge of setting up the PC that caused
the inability to just find the file and open it up.

duane

I think it was John who suggested CPYFRMSTMF or CPYFRMIMPF. I would avoid
CPYFRMSTMF as it generally has too many limitations--e.g., the to-file
must be a source physical file or program described physical file. However
CPYFRMIMPF works quite nicely to do this function. We use it regularly.
And if the folder on the PC is shared, you should be able to access it via
the QNTC file system. The main limitation for CPYFRMIMPF is that the data
must have some kind of structure to it.

All this said, but RDi doesn't really anything to do with this--except
maybe writing the code to do the import. I would post a message on
MIDRANGE-L if you need more assistance.

Michael Quigley
Computer Services
The Way International
www.TheWay.org