RE: Program user profile, adopted authority, and named activation groups

Hi David,

Is the procedure in the Service Program using SQL? And if yes is the SQL procedure using a Dynamic SQL statement? If yes, adopted authority may not apply.

There is an SQL Compile option that controls if adopted authority applies to Dynamic SQL statements.

Look at the following compile command or the set option in the SQL procedure.

CRTSQLRPGI DYNUSRPRF(*OWNER)
EXEC SQL SET OPTION DYNUSRPRF = *OWNER;

Rob W

On Nov 10, 2025, at 1:0 PM, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

Folks:

I'm having a brain cramp wrt authority and activation groups.

I have program 'A' that has *OWNER as it's 'user profile' attribute,
running in a specific named activation group. This program is calling
a procedure in a service program that has *USER as it's 'user profile'
and 'use adopted authority' is *YES. The service program has it's own
named activation group.

Will the procedure run with the authority of the owner of program A,
or will it use the job users authority because it's in it's own
activation group?

Thanks!

David
--