× 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.



Thanks Alan, but Program A and Program B have the same usrprf(*OWNER) and all files are *EXCLUDE. So I should not have this problem because program A is ok but not B. But I do.

Alan Shore wrote:
You will have to do EXACTLY the same thing for Program B and whatever files
that program requires

Ah yes - Security.... it brings back memories.... NONE of them good, a real
pain the @#$$$$$ to get to the final result



Alan Shore
Programmer/Analyst, Direct Response
E:AShore@xxxxxxxx
P:(631) 200-5019
C:(631) 880-8640
"If you're going through Hell, keep going" - Winston Churchill

but


George Lopez <georgerl@worldpa c.com> To Sent by: RPG programming on the IBM i / rpg400-l-bounces@ System i <rpg400-l@xxxxxxxxxxxx> midrange.com cc Tim Zils <timz@xxxxxxxxxxxx>, Rick Zhang <rickz@xxxxxxxxxxxx>, Mike 04/29/2010 02:06 Hellweg <mikeh@xxxxxxxxxxxx> PM Subject Re: Edit Object Authority for Library, Program, File and Please respond to User Security..... RPG programming on the IBM i / System i <rpg400-l@midrang e.com>



I changed programs to usrprf(*owner), libraries to AUT(*use) and files
to AUT(*exclude). Programs have usrprf(*owner). So in interactive
environment if I call a program A directly from a menu the access to the
files with *EXCLUDE now works. But I am getting CPF4101 error message
when I am calling a program B from program A.


Additional Message
Information


Message ID . . . . . . :
CPF4104
Date sent . . . . . . : 04/29/10 Time sent . . . . . . :
09:15:51


Message . . . . : User not authorized to operation on file xxxx01 in
*LIBL,
member, device, or program device
*N.


Cause . . . . . : User not authorized to the file, library, member,
or
device/program
device.
Recovery . . . : Obtain authority from the security officer or
object
owner, and then try the request
again.

Simon Coulter wrote:
On 28/04/2010, at 6:47 AM, Jerry Adams wrote:


If USERA is running PGMA in LIBA (with adopted authority suitable
for the file), and the file/table exists in LIBB (to which USERA is
*Exclude), would the program be able to access the file?

As long as the owner of PGMA has suitable authority to the file in
LIBB then yes.


Would a USROPN or a system-open make any difference?

No.

A comment on the previous appends: If you need to add an *EXCLUDE
library to the library list then this must be done either in an
adopting program or from a program that inherits authority from an
adopting program higher in the stack. As I recall such a library
cannot be specified in the user's sign-on job description because the
initial library is built before the initial program is given control
thus adopted authority is not yet in place.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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.