RE: 57nnQU1

The RUNSQLSTM is a great command and helps move you into the SQL world with training wheels.
http://wiki.midrange.com/index.php/SQL (which uses SQL syntax and the QM engine.)

From an SQL statement like RUNSQLSTM ' SELECT A.*, B.* from FileA A join FileB B on KeyA = KeyB '

and using F4 to name your output file, there is no need to crank up old WRKQRY to get an *OUTFILE.
You can do this with the custom RUNSQLSTM command.
(The real power of this custom command is that it can put SQL results to green screen.)

RUNSQLSTM
SQLSTM('SELECT A.*, B.* from FileA A join FileB
B on KeyA = KeyB ')
OUTPUT(*OUTFILE)
OUTFILE(MYLIB/MY_OUTFILE)

message: 7
date: Thu, 25 Sep 2014 09:09:38 -0400
from: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
subject: RE: 57nnQU1

I use both, each has their own advantages.
Use query to join files, output results to an outfile.
Haven't ever done this with SQL.

SQL search, replace, and update capabilities are superb. Can't really do this with query.
SQL index engine out performs the query index engine.
Paul