RE: Simplest Way to run SQL in a CL?

[vhamberg@xxxxxxxxxxx]

If you are using RUNSQLSTM, the source file record length might have to be 92. If using STRQMQRY, the source file record length HAS to be 91.

As my colleague across the aisle just said, easiest way to do something in CL is with a CL command - STRQMQRY even lets you substitute values, so you can even have completely ad hoc SQL statements, variable values. You don't even REALLY need a source member - can use STRQM if you have the SQL licensed program. Otherwise, everything is on the system. WRKQMQRY, CRTQMQRY come to mind. Be sure to use STRQM in SQL mode, not Prompted mode.

HTH
Vern

-------------- Original message -------------- 
From: "Eric Lehti" <elehti@xxxxxxxxxxxxxxxxxx> 

> Tim, 
> I believe you can put your SQL source code in the same source file as 
> all your other code. 
> Nothing special about the source file 
>
> > But I was trying to keep all the code in one source file, so having to 
> use a sql member file defeats > my purposes. 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l.