|
Or, even better, put those SQL scripts in a real DB2 table instead of using
separate text files or source members. That way, you can easily run SQL
queries to find your desired scripts (ex: search for a specific table or
column name), or even easily run SQL UPDATE statements to change the
scripts in bulk.
Run them using a central custom SQL script processor, which
allows centralized error handling, error logging, and performance logging.
It also facilitates the ability to extend SQL's capabilities to things like
conditional execution of SQL statements within a script.
Mike
On Wed, Jun 29, 2022 at 2:46 AM Brian Parkins<goodprophet.bp@xxxxxxxxx>
wrote:
Frank, interesting that you used embedded SQL.
Was there a reason that SQL scripts (text files) were not acceptable?
(These could then be used through an number of SQL processors such as
RUNSQLSTM or the ACS Run SQL Scripts interface.) Even a CL program
containing RUNSQL statements seems less involved than writing SQLRPGLE
programs for "housekeeping".
Just curious. (Applaud the approach!)
Brian.
As an Amazon Associate we earn from qualifying purchases.
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.