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

-----Original Message-----
message: 1
date: Wed, 10 Dec 2025 14:57:03 -0500
from: smith5646midrange@xxxxxxxxx
subject: RE: New Idea about Rpg program, copy members and RDI

I have done the function thing in copybooks when the function needs to
adopt ALLOBJ authority. If I put the function in a service program and the
service program adopts ALLOBJ authority, anybody can bind to that service
program and call the function with ALLOBJ authority. Maybe there is a way
for service programs to adopt the authority of the *PGM that is calling
functions in it but I wasn't able to figure it out.