Secured OUTQ's Circumvented by Operations Navigator -- 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.

Subject: Secured OUTQ's Circumvented by Operations Navigator
From: Graham Scott <graham.scott@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 26 Jul 2005 15:37:23 +0100
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I secured a couple of "sensitive" outq's by using OPRCTL(*NO) AUTCHK(*OWNER) 
and AUT(*EXCLUDE) then making authorised users a member of the group that owns 
the outq. Since upgrading to V5.1 I now find that users can get to the queue 
using Operations Navigator's "Printer Output" thus circumventing my well-laid 
plan. Is there any way of stopping them without removing "Basic Operations" 
from OpNav? 


Regards

Graham Scott
Operations Manager
* Tel: 01246 212248
*  Fax: 01246 212384

As an Amazon Associate we earn from qualifying purchases.

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.