Re: ADOPTED AUTHORITY WITHIN CL

[asoderlund@xxxxxxxxx]

JGracetri@AOL.COM on 07/01/99 03:23:29 PM

Please respond to MIDRANGE-L@midrange.com

To:   MIDRANGE-L@midrange.com
cc:    (bcc: Arlene M Soderlund/NFCNA.COM)
Subject:  Re: ADOPTED AUTHORITY WITHIN CL




HAS ANYONE USED THIS.
I HAVE A BATCH JOB WHICH IS RUN BY THE USER
BUT NEEDS TO USE A FILE WITH SECURITY DENIED TO THE USER.
SOMEWHERE I HEARD OR READ ABOUT ADOPT AUTHORITY, WOULD ALLOW THE JOB TO USE
THE FILE IF THE ADOPTED AUTHORITY WAS GRANTED.


     Happens all the time in packaged software.  Change the owner of the program
to a profile that would have authority, then use the change program command with
adopt authority *yes and usrprf *owner.

CHGOBJOWN OBJ(PROGRAM) OBJTYPE(*PGM) NEWOWN(QSECOFR) CUROWNAUT(*SAME)
CHGPGM PGM(PROGRAM) USRPRF(*OWNER) USEADPAUT(*YES)






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