Re: Problems with adopting authority.

[rob@xxxxxxxxx]

Owner of the program is QSECOFR.  And this has all the special 
authorities, including *ALLOBJ and *SECADM.

Perhaps there is an issue with QCAPCMD, in which the *SECADM works, but 
maybe not the *ALLOBJ?

It has been suggested to me that I use a CL program instead.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"Ed Fishel" <edfishel@xxxxxxxxxx>
Sent by: midrange-l-bounces@xxxxxxxxxxxx
03/21/2003 02:20 PM
Please respond to Midrange Systems Technical Discussion
 
        To:     Midrange Systems Technical Discussion 
<midrange-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Problems with adopting authority.



Rob Berendt asked:

>>...if it can run the CRTUSRPRF why can't it access the group?<<

It depends on the authority of the user profile that owns the program that
is using adopted authority. The help text for CRTUSRPRF says:

-------------
Restrictions: The user of this command must have:

 o  Security administrator (*SECADM) special authority

 o  Use (*USE) authority to the initial program, initial menu, job
    description, message queue, output queue, and
    attention-key-handling program (if specified)

 o  Change (*CHANGE) and object management (*OBJMGT) authorities to
    the group profile and supplemental group profiles (if
    specified).
--------------

So if the user profile that owns the program does not have *ALLOBJ special
authority then either it, or the caller of the program must have at least
*CHANGE plus *OBJMGT authority to the group profile.

Ed Fishel,
edfishel@xxxxxxxxxx


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