Trigger should be able to adopt autority. Maybe your trigger programs
uses dynamic SQL, if so, they must be compile with the option
DYNUSRPRF(*OWNER). By dynamic SQL, I mean that the SQL statement to run
is not known at compile time.
"Mackie, Roger L. (Precision Press)" <RLMackie@xxxxxxxxxxxxx>
2007-04-03 08:50 >>>
I am working on a project to give a specific user (LMTUSR) limited
access to our database. As currently designed, LMTUSR is excluded from
all but one library. The external stored procedures (SQLRPGLE and
RPGLE)
in that library adopt the owner's authority to access functions and
data
in other libraries. As long as those functions are in modules that
only
read the data, they work fine. However, the project requires
procedures
to insert data in certain tables that have *BEFORE *INSERT and *BEFORE
*UPDATE external triggers.
From reading the security reference manual (we are on v5r3) I
understand
that triggers do not adopt authority from programs earlier in the call
stack. Changing the external trigger programs to adopt authority
(CHGPGM
PGM(EXTTRG) USRPRF(*OWNER)) did not allow LMTUSR to open the files for
update using adopted authority. When the triggers are disabled, UDFs
that access the files complete correctly. When the triggers are
enabled,
the process fails with SQL0443 and CPF4236 "Not authorized to open.."
in
the job log. I could not find a parameter on the ADDPFTRG command to
adopt authority.
Did I miss something? While using adopted authority is there a way to
insert and/or update data into files with triggers? If not, I'll
probably use a data queue to get the data to a job whose user does
have
authority. Or is there a better way?
Thanks,
Roger Mackie
midrange.com
