Re: SQL subquery? sub-something?

["colin williams" <colin.williams@xxxxxxxxxxxx>]

Dan,

what I have done is similar to what your describing. Created a source member
in QDDSSRC for the view, so that it resides in the same source member as all
the other files, and use RUNSQLSTM to create the file. In the source member
I leave additional notes on how to create the file.

cheers
Colin.W
----- Original Message ----- 
From: "Dan Bale" <dbale@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, August 17, 2004 9:26 PM
Subject: RE: SQL subquery? sub-something?


> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx / Colin Williams
> > Sent: Tuesday, August 17, 2004 10:14 AM
> >
> > Sounds like the SQL view would be the easiest, then create any
> > additional indexes as usage dictates in the future
>
> Thanks Colin!
>
> What is the standard convention, if there is any, for storing the "source"
> of the SQL DDL?  I created this in the interactive SQL program.  I can
> copy/paste it into a source member having the name of the view.  Is there
a
> member type to use that identifies it as DDL for a view?  I would like to
be
> able to use PDM option 14 or 16 on a source member run the SQL in it, to
> create the view, much like we use 14 to compile files.  I *could* just
> create a PDM option to RUNSQLSTM, but I've got 14 & 16 memorized!
>
> db
>
> --
> 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.
>
>


This e-mail has been sent by a company of Bertram Group Ltd, whose registered 
office is 1 Broadland Business Park, Norwich, NR7 0WF. 
This message, and any attachments, are intended solely for the addressee and 
may contain privileged or confidential information.  If you are not the 
intended recipient, any disclosure, copying, distribution or any action taken 
or omitted to be taken in reliance on it, is prohibited and may be unlawful.  
If you believe that you have received this email in error, please contact the 
sender immediately. Opinions, conclusions and statements of intent in this 
e-mail are those of the sender and will not bind a Bertram Group Ltd company 
unless confirmed in writing by a director independently of this message. 
Although we have taken steps to ensure that this email and any attachments are 
free from any virus, we advise that in keeping with good computing practice the 
recipient should ensure they are actually virus free.