Re: Another SQL question: This time with VIEWs

[Jeff Young <cooljeff913@xxxxxxxxx>]

Why not just use a call to QCMDEXC to issue the RUNSTQSTM?

 
Jeff Young 
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2 
IBM  Certified Specialist- e(logo) server i5Series Technical Solutions 
Designer V5R3
IBM  Certified Specialist- e(logo)server i5Series Technical 
Solutions Implementer V5R3 

  
 






________________________________
From: Vern Hamberg <vhamberg@xxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Fri, April 22, 2011 6:24:05 PM
Subject: Re: Another SQL question: This time with VIEWs

Ja,es

I'm working - or walking - off a really long plank here - there is an 
INCLUDE function for embedded SQL. It seems that some of the embedded 
stuff can be used in RUNSQLSTM, but, as I say, this is really a very 
wide-area guess!

Eh?
Vern

On 4/22/2011 4:55 PM, James Lampert wrote:
> Schutte, Michael D wrote:
> > I'm confused.  You're wanting to programmatically generate the sql for what?  
> > The view?
> I wasn't asking how to programmatically generate the SQL for an already
> extant view; the object is to generate SQL for a new view, with
> field-renaming and calls to my "DISPLAYVAL" UDF where applicable, and
> with a WHERE clause that calls some customer-specific censorship UDF,
> when the based-on PF is modified and regenerated: the sole purpose of
> the view (one of many) is to provide a "new data access layer" by which
> SQL-based reporting tools can access the application database with (1)
> field names based on the PF's column headings, (2) "table-driven" fields
> resolved from their internal coding to what is shown in the application,
> and (3) any censorship the customer imposes on the database preserved.
>
> The only question was, given a source member containing SQL source for
> RUNSQLSTM, is there a way to "INCLUDE" other source members, analogous
> to "/COPY" in ILE RPG, or "#include" in C?
>
> --
> JHHL