Re: Questions on USING ADOPTED AUTHORITY

There are two program attributes of concern.
First is USRPRF or "User profile". In a traditional "program only access"
scenario only the first program in the stack should have this set to
*OWNER.
The second is USEADPAUT or "Use adopted authority". This one looks at the
program which called it and, if that program adopted authority then it
will also.
Many programmers set these both without even thinking why there are two
different parameters.
Infor LX has their initial program (BPCSMENU) set up with USRPRF(*OWNER)
all the rest of their programs are set with USER(*USER) USEADPAUT(*YES).
You do NOT need to set USER(*OWNER) on each and every program if you are
using USEADPAUT(*YES).

You do NOT need program source to modify this. A simple CHGPGM command
works wonders.

Caution: IFS operations could not possibly care less about program
adoption and ignore it. Therefore that needs a different solution. The
recommended one is to use the "profile handle" API's to run under a
different user. This is how you see those jobs like
Job 109579/QUSER/QZRCSRVS
Now servicing user ROB
or some such thing. See also WRKOBJLCK ROB *USRPRF to find some of these
jobs, replacing ROB with your user id.
Some people stopped learning anything new back in the 80's and they will
just submit a job to run under the desired user to handle the authority.
Of course, your audit journals will then be all muffed up.



Rob Berendt