× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi,

I'm reviewing the setup of our outq authorities and found we have many 
different settings. 
We have about 60 printers/outq and several other outq w/o printer attached.

I want to do the following setup:

Outq description has parameters "show all files" and  "authority?" which I want 
to set to
*no and *dtaaut.
The outq object will get a general *public *use and special authorities *add, 
*read, *delete
for specific group profiles.

Lets say, all users of group WAREHOUSE should be able to do everything on the 
warehouse 
printers,  and at least should be able to handle their own spoolfiles on other 
printers.


Will this work or did I miss something? There is no business need to protect 
specific outqs, 
but I'd like to separate them by application. 

Are there any security issues when using OpsNav on printers/outqs?

Is it possible to let somebody print/change a spoolfile, but not delete it? 
Here I also mean 
when save *no on the spoolfile is active - it then would be deleted after 
printing?

Any other issues?

Regards,

Oliver

ps. we are at V5R2

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.