RE: New Idea about Rpg program, copy members and RDI

It has been a while but I'm going to guess they were not in the same
activation group and that was my problem. If you still have your test
program handy, can you test again with different activation groups? If
you've already cleaned it up, I will try it later.

-----Original Message-----
From: RPG400-L <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Michael
Quigley
Sent: Thursday, December 11, 2025 10:21 AM
To: rpg400-l@xxxxxxxxxxxxxxxxxx
Subject: RE: New Idea about Rpg program, copy members and RDI

Service programs already use adopted authority from the calling program. The
only difference is I don't believe you can tell a service program to not use
adopted authority like you can on a program. I thought this was true, but
was puzzled by your comment that you couldn't figure out how to do it. So I
wrote a quick test creating a file with *PUBLIC *EXCLUDE, writing a quick
module to display the object description, creating a service program with
that module, and then creating a program with USRPRF(*OWNER) and owned by a
profile with *ALLOBJ authority. If I try to display the object description
of the test file from a command line, I get the CPF2189 escape message "Not
authorized to object...." But if I call the *OWNER program, the module does
the DSPOBJD and works fine.

This makes sense to me because the service program is running in the calling
program's activation. It doesn't have it's own.

Thanks,
Michael Quigley
Computer Services
www.TheWay.org