RE: Active joblog security

Ed/Rob - Thank you, thank you!!!!  

This has been a thorn in our side for quite some time and our operations
manager was asking for *ALLOBJ for the operators since they couldn't
view active joblogs for power users.  I just used the CHGFNCUSG for our
OPER group and now all the operators can see these joblogs.

I really, really didn't want to give *ALLOBJ to operations.  They have
enough loaded guns to hurt us without giving them a bazooka too!   (:o)

Glenn Birnbaum
Platform Technology Services, REI
253-395-8206
"Get Outside Yourself":  http://www.rei.com


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ed Fishel
Sent: Wednesday, August 03, 2005 1:52 PM
To: Midrange Systems Technical Discussion
Subject: Re: Active joblog security

If you use a V5R3 system you can also use one of these commands to
change the default authority or give a specific user authority to this
function.

CHGFCNUSG FCNID(QIBM_ACCESS_ALLOBJ_JOBLOG) DEFAULT(*ALLOWED) CHGFCNUSG
FCNID(QIBM_ACCESS_ALLOBJ_JOBLOG) USER(user-profile)
USAGE(*ALLOWED)

Both the CL command and GUI methods apply only to a job log of an active
job.  Also, even after you give someone authority to the
QIBM_ACCESS_ALLOBJ_JOBLOG function, they will still need to have *JOBCTL
special authority to use DSPJOBLOG to view the job log of another user.
Once the job log has been printed, authority to this function does not
help because the authority rules for spooled files takes over.

Ed Fishel,
edfishel@xxxxxxxxxx