> It sounds to me like the program is using the authority of the programs
> owner and not that of the user.  Change the program to use user authority
> give the owner the authority to perform the task.

I don't think that this is possible.  Aopted authority is cuulative, meaning
that when you adopt the authority of another user you get the combined
authorities of both users.  It's not exclusive the way that swapped profiles

> I created a file.  If I clear the file (clrpfm) from the command line, all
> is well.
> If I call a program from a command line that clears this file, I get an
> error message saying that I am not authorized.

Assuming that you call the program from the from the same session (indeed
the same command line) that the clrpfm was run, there is one scenario that I
can think of that could cause this...

-You are not authorized to clear FILE1.
-USER1 is authorized to clear FILE1.
-PROGRAMA adopts it's owner's authority (USRPRF(*OWNER)).
-You call PROGRAMA.
-You access a command line while PROGRAMA is still open.
-You are able to clrpfm FILE1 because you are running under PROGRAMA which
adopts USER1's authority.
-You access a PROGRAMB while PROGRAMA is still open.
-PROGRAMB states "Use Adopted Authority=*NO"  (USEADPAUT(*NO))
-You are not able to clrpfm FILE1 because PROGRAMB has stipulated that you
are not to acquire adopted authority from a previous program (PROGRAMA in
this case).

Does that fit?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.