Re: Securing an outq -- MIDRANGE-L

× 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.

Look in the archives for SPLCTL and JOBCTL. OUTQ security is a little weird. You should probably refer tot he Tips and Tools for Securing Your iSeries. To quote,

A user with *SPLCTL special authority can see any spooled file on the system, no matter what efforts you make to secure your output queues.

There is a section in the Security manual on Printing in the Work Management chapter (near page 186). Read until you understand it well.

Clearly you need to check for users with *SPLCTL special authority. There're reports in GO SECTOOLS that'll show this, including mismatches between user class and special authorities. There's also a PRTQAUT command that can be called from that menu.

HTH

Vern

At 10:51 AM 6/23/2003 -0400, you wrote:

Is there a way, short of running a third part application to secure an
outq. I've tried giving *public *exclude authority to the outq, but users
can still see the outq and its contents. Maybe an exit point or something.

Thanks,

Mark

Mark D. Walter
Senior Programmer/Analyst
CCX, Inc.
mwalter@xxxxxxxxxx
http://www.ccxinc.com

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.