Personally I would never use RUNSQLSTM in a production environment. If
someone goes into the member and fat fingers something they've just hosed
your process altogether. At least if it's a compiled program you don't
have to worry about that biting you.


Thanks,
Tommy Holden



From: Robert Clay <zreclay@xxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx,
Date: 03/28/2013 02:00 PM
Subject: RunSQLStmt in production
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Do you use RunSQLStmt in production environment?

Our team is beginning to use it more and more on a 6.1 system and I am
curious as to the intelligence of using it as opposed to SQLRPGLE
programs and imbedded/static SQL statements where one can logically trap
for errors using SQLSTATE and GET DIAGNOSTICS, etc.

Your thoughts? Can you think of reasons pro or con?





This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2026 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.