× 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.


  1.  Home
  2. MIDRANGE-L
  3. March 2019

Re: Storing SQL script options

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 03/26/2019
11:53:44 AM:
I've just recently started using the ACS "Run SQL Scripts".
I'm looking at the various options available for storing SQL
statements, some for IBM i catalog tables and views.
My initial option was to create a source member in our source
library for each SQL script.
With the 10 character limit, I'm finding it difficult to have
meaning names for these scripts.

What methods are others in the group using to store SQL scripts?


We don't allow SQL to generate the system name for our SQL
objects. Therefore, we have no trouble storing the SQL in a standard
source file using the desired system name as the member name. We do,
however, create our own source files (e.g., SQLTBLSRC, SQLIDXSRC,
SQLVIEWSRC) using a wider line format for better readability. We just
have to specify the MARGIN parameter at RUNSQLSTM time.


Sincerely,

Dave Clark

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.