RE: Active joblog security

I'm going to go out on a limb here and assume that your developers have
no other need for *JOBCTL or *ALLOBJ authority.  I would create a
command/program for them that adopts the required authority and then
does a DSPJOBLOG for these jobs.  We had to do this here for programmers
who needed access to the joblogs of a profile with *ALLOBJ (after we
took *ALLOBJ away from them.)

If you like send me an email ofline and I'll forward the code to you.

Regards,
 
Scott Ingvaldson
iSeries System Administrator
GuideOne Insurance Group

-----Original Message-----
date: Wed, 3 Aug 2005 12:52:36 -0500
from: "Reinardy, James" <jreinardy@xxxxxxxxxxxxxxx>
subject: Active joblog security


I have a group of developers that would like to be able to monitor
active jobs that are started by our LXI scheduler.  These are attached
to a system login called CSP.  If they go into WRKACTJOB, they can use
nearly any option except display job log, option 10.  When they do that,
they get "Not Authorized to display job log".  Once the log is on the
OUTQ, they can view it just fine, and those of us with QSECOFR level
authority can display the active job log without any issue.  I have
tried giving them read and execute authority on the CSP login, to no
avail.  Any ideas on what I might look at to allow this?

Thanks,

Jim Reinardy
Badger Meter, Inc.