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

You seem to be leaving out a lot of information. Where is the business
logic running? On the AS/400 or in the client. Is this just a GUI front end
or the whole application runs on the client?

You can write stored procedures in stored procedure language which complies
to C code and runs on any platform but that may or may not make sense on
what you are doing. If you are using the machine strictly for database
access stored procedures may not be the way to go.

If the business logic runs on the AS/400, I definitely would not recommend
using stored procedures. Abstract the interface away. Just send messages
via a mediator letting the front end be anything you want it to be.

If you are writing all the business logic on the 400, then COBOL is
probably the most portable.

On Mon, Aug 27, 2012 at 3:36 PM, James Lampert <jamesl@xxxxxxxxxxxxxxxxx>wrote:

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
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.