In that case you will need a program to interrogate error conditions and
report any potential failures to the operations staff.  
Performance also may be an issue and in that case you might need to build
some indexes for embedded SQL.  This should be a factor in deciding SQL vs
RPG.

In my view, most important thing is the ease of interrogating error
conditions and ability to inform the operator successfully, consistently and
with actionable information (i.e. network connection failed - strtcp, or
file is in use - end this job that is holding the lock etc.).

Just the fact that you need to write a controller type program may drive you
to do it all programmatically.

Elvis

-----Original Message-----
 Subject: RE: SQL Vs. RPG Opinions

It will be something that will execute on a nightly basis. I'll be
refreshing the target database every night. Also, the logic is a bit
tricky. 




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