Question

  Asked: Jul 11 2005   2:09 PM GMT
  Asked by: bkr0963c


Is *JOBCTL needed to view job logs?


OS/400, iSeries, i5, Backup & recovery, Hardware, Installation, Integration/Connectivity, Logical partitions, PC/Windows Connectivity, Performance/Tuning, Printing/Output, PTFs, Security, Server consolidation, System monitoring, Tools, tips and tricks

I have read IBM's Security manual and Work Management manual and I know that *JOBCTL is needed to change job priorities and other things for jobs on the system, but I do not see any statements that say *JOBCTL is needed to view the job logs of other user's jobs on the system. Does anyone know if this is the case? I am going to test it to find the answer, but I would like to know without testing if possible. Thanks for the help.

Subscribe to Alerts! Get questions and answers delivered to your Inbox.


E-mail me updates on this question



   SUBSCRIBE

hidden modal window

Answer Wiki (Improve, edit or add to this answer)


 RATE THIS ANSWER
0
Click to Vote:
  •   0
  •  0



You can view your own joblog without it, but must have that authority in order to see *someone elses* joblog, yes.
  • AddThis Social Bookmark Button

Browse more Questions and Answers on AS/400, Storage and DataCenter.

Looking for relevant AS/400 Whitepapers? Visit the Search400.com Research Library.


Discuss This Answer


You must be logged-in to discuss a question. Log-in/Register

TheQuigs  |   Jul 12 2005  8:25AM GMT

It depends on the security configuration of the outque where your joblogs go. By default this is QEZJOBLOG.

If DSPDTA is *YES, then you could display any spoolfile in the queue. This can be set in combination with AUTCHK(*DTAAUT) which means to check the data authority to the output queue. If you set it this way (using the object authority on QEZDEBUG), you can control who can display job logs.

It’s something you want to consider — who you want to allow to see any job log.

 

TomLiotta  |   Jul 13 2005  1:44PM GMT

You haven’t quite clarified your question enough. The term ‘joblog’ has at least two very different usages. First, you can view the ‘joblog’ of a running job by using a command such as DSPJOB OPTION(*JOBLOG). And second, you can view the spooled file named QPJOBLOG that is created when a job ends and the job attributes are set to create that spooled file.

The two need not contain the same items and authorities may be very different for viewing one or the other.

Tom