Home > IT Answers > AS/400 > Difference Between *SPLCTL and *JOBCTL
Rickmcd
1,480 pts.
 Difference Between *SPLCTL and *JOBCTL
*JOBCTL special authority, *SPLCTL special authority, AS/400 security
I have heard you should not use *SPLCTL but *JOBCTL for Authorities. Why?

Software/Hardware used:
ASKED: February 12, 2009  6:34 AM
UPDATED: November 4, 2009  2:43 AM
RELATED QUESTIONS
Answer Wiki:
Hi, *SPLCTL and *JOBCTL are 2 completely different authority settings. They give you the authority to do completely different things. Both can be used separately or together, depending on what you want to achieve. Regards, Martin Gilbert.
Last Wiki Answer Submitted:  February 12, 2009  10:46 am  by  Gilly400   23,625 pts.
All Answer Wiki Contributors:  Gilly400   23,625 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

Rickmcd,
It depends on what the user will be doing.

Job control (*JOBCTL) special authority gives the user the authority to change, display, hold, release, cancel, and clear all jobs that are running on the system or that are on a job queue or output queue that has OPRCTL (*YES) specified. The user also has the authority to load the system, to start writers, and to stop active subsystems.

Spool control (*SPLCTL) special authority to users who need to perform all spool-related functions. A user with *SPLCTL special authority will always have the power to start, stop, hold, alter, and read all spooled objects on the system.

If we are talking about a system operator, then I can see where they may need these special authorities, but even then I would think twice. Never would I give these authorities to the average user.

There is an article at http://systeminetwork.com/article/jobctl-or-splctl that gives a good explanation of what these authorities allow the user to do.

Teandy
 5,830 pts.
 

Note that these special authorities give the capability to work with all jobs and all spooled files, regardles of whose jobs or spooled files they are. These special authorities are not needed just to work with your own jobs and spooled files.

E.g., a user with *SPLCTL can work withyour spooled files even if you spool them to an *OUTQ that the user has *EXCLUDE authority to. That is, the “special” authority overrides the individual authority that you wanted to impose.

That’s an example of why they’re called “special”.

Tom

TomLiotta
 108,310 pts.