×
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.
On 5/21/20 9:42 AM, Gerald Magnuson wrote:
so my users that need file transfer and excel to bring down data,
they need to be as *all or *change authority? because if I just give
them *use, then their green screen apps won't work (they can't update
data anymore)....
having their group profile in authority list trumps adoptive authority?
how is this supposed to work?
I realize this may be a big change, but what about setting the program to use
owner authority and changing the program owner to a profile that can update the
file?
That way you can remove the users authority to update the file. They will be
able to read it, but not update. When the program runs, the authority used will
be that of the *PGM object's owner.
So, create a application owner profile that has authority to update the file.
Change the owner of the program to the new profile.
Change the program to use *OWNER as the USRPRF attribute: 'CHGPGM PGM(ABC/XYZ)
USRPRF(*OWNER)'
You may need to control access to the program itself if you don't control access
at the application level.
david
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
