On Thu, Oct 1, 2015 at 5:07 PM, Kelly Cookson <KCookson@xxxxxxxxxxxx>
wrote:

2. I have a very vague idea that moving business logic and
development
from COBOL into DB2 as much as possible is a good thing. But I don't
really understand. I can't explain what this means, why we should do
it, or offer a few good examples. Would someone mind briefly sharing
some ideas or talking points for a good elevator speech?


One example is you can use features like record level access to handle
security at the database level. Security is certainly business logic.
Securing the data at the lowest level means that no matter how you rewrite
your presentation layer (your end user application) the security is already
there. You could give a power user the ability to write raw SQL queries,
write a web app, or call SQL from COBOL, and all your users have the same
level of access.

Secondly, if your accessing two files row by row looking for matching
fields for a report in COBOL, you can totally do that with a simple select
statement that you can wrap in a stored procedure. You can then tune that
SQL, add indexes and call that stored procedure from PHP or whatever.

Hope those are good examples.

Justin

This thread ...

Follow-Ups:
Replies:

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

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