× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



My personal preference is to operate in *SQL naming for DDL. The first thing I usually do is create an owner profile, named the same as the schema. Logon as that user, run the creation script. Poof.

Then, if we need another schema (library) with those same DDL created objects, create a new profile, logon, run... poof... copy number 2.


Mike Cunningham wrote:
Is there any support in V6R1 that would allow parameters to be passed to the RUNSQLSTM command that could be used in the SQL source as variables?
Say you have a source file with a "CREATE VIEW PRODUCTION/VIEW..." command but sometimes you need to create that view in a development library and you want the command to be "CREATE VIEW DEVELOPMENT/VIEW..." It would be nice to be able to do a RUNSQLSTM PARM(DEVELOPMENT) and have the source "CREATE VIEW &LIBRARY/VIEW..."

Or is the solution to just code "CREATE VIEW VIEW..." and make sure your current library is set to where you want the object created?


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.