AW: Access control -- forcing use of stored procedures for update

Programs and procedures without return values written in RPG, CL or any
other HLL (High Level Language) can be registered as external stored
procedure.
Functions written in RPG (or any other HLL) can be registered as external
User Defined Function.

Registered External Stored Proceudres and User Defined Functions can be
called from any interface that allows to use SQL and connect to your Power I
(please do no longer use the outdated term AS/400).
External stored procedures are called with the SQL command CALL.
UDFs are used like any SQL scalar function.

Stored Procedures and UDFs can also be written in SQL programming language,
which is pure SQL but under the covers converted into C with embedded SQL.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"

-----Ursprüngliche Nachricht-----
Von: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] Im Auftrag von James Lampert
Gesendet: Monday, 27.8 2012 23:36
An: Midrange Systems Technical Discussion
Betreff: Access control -- forcing use of stored procedures for update

I'm currently researching how to convert a client-server application from a
proprietary AS/400-only server running a proprietary communication protocol
to a JDBC/SQL-based solution that can be ported to other DB2 platforms.

Can I protect a table so that (unless you have a privileged account that is
allowed to do database surgery) updates can only happen through stored
procedures?

Can the stored procedures be set up so that the real work is done in a HLL
program (typically RPG on AS/400 boxes, some other language, hopefully not
C, on other DB2 platforms), that can be recompiled freely, without having to
in some way tell DB2 that there's a new version?

--
JHHL