MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » November 2008

Re: Giving read access to a spool file



fixed

You can give the contractor *SPLCTL

If you don't want to go that far, you can change the authority on the
output queue to AUTCHK(*DTAAUT) and then use the output queue authority to
cover who can access it (I think a separate thread just covered this,
search on AUTCHK or DTAAUT

If you system is essentially open, but he can't see your job logs, maybe
it is because you have *ALLOBJ and he doesn't.
Granting access to job logs created by programs with *ALLOBJ to users
without *ALLOBJ, use:
WRKFCNUSG: Work with Function Usage
Add users to the function:
QIBM_ACCESS_ALLOBJ_JOBLOG Access job log of *ALLOBJ job
===============================================
Tom Kreimer
Network Manager
Buckhorn Inc, Milford OH



Charles Wilt wrote:
If they are your own spool files, you have full access to them.

That's just it: it *is* my spool file; I'm not the one with the access
problem. (Actually, my account being QSECOFR-equivalent, I can look at
whatever spool files I damn well please.)

There is a contractor on the box, who needs to see one of mine (and may
eventually need to see any number of mine), and I don't want to give him
a privileged account.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact