×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
USRPRF(*OWNER) and USEADPT(*YES) are two unrelated things. Well maybe not
unrelated but it makes no sense for a program to have both.
USRPRF(*OWNER) says to not use the authority of the user currently running
the program but to adopt the authority of the person who owns this program
instead.
USEADPT(*YES) says if there is an unbroken chain of USEADPT(*YES)
throughout the call stack all the way up to some program which does
USRPRF(*OWNER) then to use that adopted authority. For example, let's say
you have an intitial program called BPCSMENU and it is owned by SSA and it
has USRPRF(*OWNER). BPCSMENU calls PGMA owned by SMITTY which has
USRPRF(*USER) USEADPT(*YES) then it will continue to use the adopted
authority of SSA. If PGMA calls PGMB then this chain continues until the
first program that has USEADPT(*NO).
But, yes, I would check for the presence of one or the other of these.
There are some scenarios in which adopting authority does no good. Mainly
accessing data in the stream file system outside of the /qsys.lib system.
This will require using the profile handle APIs.
Rob Berendt
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
