RE: Authority issue with a library

Mike,

In order to access objects in a library, a user needs *USE authority to
that library. They can get *USE a number of ways:
-Directly authorized to the object
-Via their own profile name,
-As an inherited right from one of their group profiles,
-Inherited from *PUBLIC's rights,
-Authorized to the object via an Authorization List
-Via their own profile name,
-As an inherited right from one of their group profiles,
-Inherited from *PUBLIC's rights,
-From adopted authority during program execution
-From the special authority *ALLOBJ (NOT recommended!)

Whichever way you choose, the user must have *USE authority to the
library at the time they first attempt to access an object in the
library. Else, you will get your "not Authorized" error.

In the case of adopted authority, it would not work to have the user
call a program that adopts authority if the program is in the library in
question. In that case, the user would never get to the program at all,
and therefore would never receive the adoption.

HTH,

jte

--
John Earl, VP and Chief Technology Officer
PowerTech: 253-872-7788
Direct: 253-479-1408
Mobile: 206-669-3336
John.Earl@xxxxxxxxxxxxx




Email is an excellent way to communicate material that is not time
sensitive. If your communication is of a more urgent nature, please
call.

===========================
This email message and any attachments are intended only for the use of
the intended recipient named above and may contain information that is
privileged and confidential. If you are not the intended recipient, any
dissemination, distribution, or copying is strictly prohibited. If you
received this email message in error, please immediately notify the
sender by replying to this email message or by telephone and delete the
message from your email system. Thank you.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Smith, Mike
Sent: Friday, August 17, 2007 7:54 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Authority issue with a library


I have a library that is secured by an authorization list. Owned by
QSECOFR. Lib name is RGIT
I do an Addlible RGIT when the menu is called.

I have a user that needs to run a program that is in this library.

The

programs are owned by QSECOFR and adopt authority. However the user
still gets a 'not authorized to lib RGIT' message.

Also,
User has another program that is in another library(not owned by

QSECOFR

or adopting). Doesn't touch RGIT.(but the lib RGIT is added when the
menu is called) This program has an interactive prompt screen(which
works just fine), and then submits a program(this program get the same
'not authorized to lib RGIT' message.

The menu is a vendor menu, so my only real option is to add the

library

via a prerun command.

I had originally added the library when the CL was called, but I
received the same authority errors.

Does this make sense? Ideas on how to correct this issue?

Thanks
Michael Smith


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.