If all tables, views and indexes are within the same library, you can remove
the qualified specification from your SQL Script (and keep only the
tables/views). Then specify the schema/library within the RUNSQLSTM option
DFTRDBCOL (=Default Schema/Library) --> F10 / Second Page
Mit freundlichen Grüßen / Best regards
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von James H. H. Lampert
Gesendet: Tuesday, 05.2 2013 18:25
An: Midrange Systems Technical Discussion
Betreff: A different SQL question, on a different SQL project
Suppose I'm creating an SQL view, FOO, joining PFs BAR and BAZ, and applying
UDFs to some of the fields, and putting it in the same library as the PFs.
And suppose we have a whole bunch of libraries, each of which contains a BAR
and a BAZ, with all BAR PFs sharing the same format, all BAZ PFs sharing the
same format, and all FOO views to share the same format.
And suppose I'm creating FOO using a RUNSQLSTM on a source member.
If I were creating FOO as a native join-logical, from DDS, using CRTLF, it
would be easy enough to either use the same source member for all instances
of FOO, or to just CRTLF one instance, and then copy it into the other
libraries that need it, just by leaving the based-on PFs unqualified in the
But is there a way to do the same with RUNSQLSTM, either creating a view
that will always be based on the PFs in the same library, or failing that,
at least use the same source member for all libraries?
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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l