|
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. :-) Would anyone happen to know the parameter list for 'QMHDSPJL'? I would like to replace this with a CL that calls the original with adopted rights. I'll probably just bite the bullet and take away *ALLOBJ but was curious if this would work. Thanks everyone for all the feedback, Mark rob@dekko.com Sent by: To: MIDRANGE-L@midrange.com owner-midrange-l@mi cc: drange.com Subject: Re: How do I give authority for *PGMR to look at job log of *SECADM? 06/06/01 08:29 AM Please respond to MIDRANGE-L You are assuming that there is a spool file. The problem is that the job is currently active. And, since many levels of OS ago, IBM won't let anyone with less than *ALLOBJ look at the joblog of a running job if the user of the running job has *ALLOBJ a dilemma is created. Often we discovered that people got into the habit of having all submitted jobs from the scheduler run under only a select few user ids - all of whom had *ALLOBJ. When we broke one guys kneecap when he requested that he have *ALLOBJ so he could look at these joblogs, the others reevaluated and decided that maybe they didn't need to run under a user with *ALLOBJ authority and changed the job scheduler to run under a somewhat more restricted user profile. Now the only job running under *ALLOBJ is the backup. And if that screws up it's just not their problem, and Peggy or I fix it. Rob Berendt ================== A smart person learns from their mistakes, but a wise person learns from OTHER peoples mistakes. MacWheel99@aol.com Sent by: To: MIDRANGE-L@midrange.com owner-midrange-l@mi cc: drange.com Subject: Re: How do I give authority for *PGMR to look at job log of *SECADM? 06/06/01 02:50 AM Please respond to MIDRANGE-L Consider having the job logs going to a spool file that the *PGMR has access to. MacWheel99@aol.com (Alister Wm Macintyre) (Al Mac) +--- | 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 +--- +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.