RE: Running SQL commands from CL (or elsewhere)

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

> Only if you had a consistant SQL statement. How would you, for example,
> > use RUNSQLSTM to insert the number of rows read by a RCVF?
>
> Well, you could write the SQL statements programmatically into the 
> source member used by RUNSQLSTM just the same as you can write the 
> statements to an IFS text file to be used by the QShell db2 command with 
> the -t -f parameters.

Except that CL can't write data to a source file (directly).  You'd have 
to call an HLL or QShell to write the records, and if you're going to do 
that, you may as well use the HLL or QShell to execute the SQL commands 
directly rather than writing it to a source file.


> My answer was just that RUNSQLSTM is another option and it doesn't require
> the ST1 LPP or QShell to be installed.  Too many of my clients
> don't install either; we "correct" that as often as possible.

Starting in V5R3, you can call the SQL CLI APIs directly from CL. That 
way, you don't need QShell or ST1.  Just another alternative...