RE: How do I give authority for *PGMR to look at job log of*SECADM?

The problem with this scenario is NOT the fact that a profile with *ALLOBJ has 
created a file, but that the library CRTAUT parameter that the file was created 
in has NOT been set appropriately. (Been there - had that done to me @ 3:04 
a.m.) 

>>> Buck Calabro <Buck.Calabro@commsoft.net> 06/06/01 04:41PM >>>
>> I agree that *ALLOBJ for our Job Scheduler user is extreme, but you
>> definitely don't get any calls at 3:00 AM for authority problems.
>>:-)
>
>Sure, if folks have *ALLOBJ they never have to call with security
>problems.  But in this case it is the calls that you don't get that
>should scare you.

I've been burnt by a *ALLOBJ job creating files during a reorg and then the
normal *USER follow-on jobs all die because of lack of authority.  That's
always good for a 0300 call.

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