Locking down an OUTQ -- MIDRANGE-L

Subject: Locking down an OUTQ
From: "Willie J. Moore" <WMoore@xxxxxxxxxxxxxxx>
Date: Wed, 14 Sep 2005 07:03:27 -0700
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 have been asked to look into locking down one of our 'outq's. It is the one 
that payroll checks go to.  Currently the following have access: *public *use, 
hds (GM) *all, and qspl *change.
I thought of doing an EDTOBJAUT and changing *public to *exclude, but was not 
sure how this would effect system saves, release upgrade, etc.
Any suggestions or pointers would be appreciated.
Thanks,
William Moore

Follow-Ups:

Re: Locking down an OUTQ , rob

This mailing list archive is Copyright 1997-2026 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.