RE: Block certain commands in interactive sql

Normal notion is that interactive SQL is the STRSQL command interface. If
that's the case, two exit points mentioned below do not apply. They apply
to database host server jobs (i.e. QZDASOINIT jobs servicing ODBC/JDBC etc.
requests).

The concept of privileges does exist in SQL though. Since it more or less
translates to object level security, just in SQL lingo, I am not certain if
that would work for you. Just in case it does, take a look at this article:
http://www.ibmsystemsmag.com/ibmi/june08/technicalcorner/20803p1.aspx

From my experience, there is no 'easy' way to accomplish what you've asked.

I would use this situation to build a stronger case for object security.

Elvis

Celebrating 11-Years of SQL Performance Excellence on IBM i, i5/OS and
OS/400
www.centerfieldtechnology.com


-----Original Message-----
Subject: Re: Block certain commands in interactive sql

There are two exit points for SQL that probably would allow you to lock
it down to inquiry only. Check QIBM_QZDA_SQL1 and QIBM_QZDA_SQL2 in
Infocenter.

Colpaert, Peter wrote:

Hi group,

one of my friends asked me the following question:

"Is it possible to allow a user to only use certain commands in an

interactive SQL session?"

What he wants to do is make sure that the user can only use SELECT and not

UPDATE, INSERT etc.

But for reasons unknown to me, object security is not an option.

Thanks,


Peter Colpaert