• Subject: Re: *SECADM change QSECOFR passw
  • From: "Simon Coulter" <shc@xxxxxxxxxxxxxxxxx>
  • Date: Tue, 24 Apr 01 11:23:30 +1000

M
Hello Dan,

You wrote:
>   Initial program  . . . . . :   SEC612R
>     Library  . . . . . . . . :     *LIBL

and

> FWIW, DSPPGM SEC612R (UKHELP's initial program) shows "Use adopted
> authority: = *YES"

Who owns the SEC612R program?  Is the user profile attribute of the program 
set to *USER or *OWNER?  If *OWNER then what authorities does the owning 
profile have?

All programs default to "Use adopted authority *YES".  That doesn't mean they 
have any special rights.  It simply means IF authority is already being 
adopted by a program higher in the call stack then this program will also use 
that adopted authority.  The real question is whether the SEC612R program 
adopts its OWNER'S authority and if that owner is QGOD.

Regards,
Simon Coulter.


 FlyByNight Software         AS/400 Technical Specialists       
 Eclipse the competition - run your business on an IBM AS/400.  
                                                                
 Phone: +61 3 9419 0175   Mobile: +61 0411 091 400        /"\   
 Fax:   +61 3 9419 0175   mailto: shc@flybynight.com.au   \ /   
                                                           X    
               ASCII Ribbon campaign against HTML E-Mail  / \   

+---
| 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
+---

This thread ...


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

This mailing list archive is Copyright 1997-2019 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].