Re: Problems with authority...

[Chris Whisonant <Chris.Whisonant@xxxxxxxxxxxxx>]

Alan, thanks for the concern.  I really wouldn't recommend copying QSECOFR, 
and I shouldn't have stated that.  I believe the original post stated that 
QSECOFR was the object owner of the current CL.  My main point would be 
that it would be better to create a somewhat powerful profile with Limit 
Capabilities *YES and change the CL's object owner to this one and create 
another CL for this other problem with the new object owner as well.

Chris

>Please be very careful with regard to using/copying the user profile 
>QSECOFR. This user profile is the equivalent of a god on the AS/400, even 
>with limit capabilities set to *YES. (As would a copy of this user 
>profile)This profile has the authority to delete anything and everything 
>from the system, change/delete other user profiles.  Change system values. 
>I could go on for quite a few screens.
>
> >>> Chris Whisonant <Chris.Whisonant@Comporium.com> 03/22/01 03:30PM >>>
>If possible, copy the QSECOFR profile (or another super user) and Limit
>Capabilities *YES on the new profile.  Then change the object ownership of
>the CL program from QSECOFR to this new profile.  We had to do something
>similar the other day and this worked.

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---