RE: Locking down an OUTQ

There was a fantastic article by Carol Woodbury in the eServer Mag this
month - page 44.

http://www.eservercomputing.com/ME2/Audiences/dirmod.asp?sid=&nm=&type=P
ublishing&mod=Publications%3A%3AArticle&mid=8F3A7027421841978F18BE895F87
F791&tier=4&id=7966522D7A01489E974FB9E7FC77B189


Justin C. Haase - iSeries System Administrator
IBM Certified Systems Expert - eServer i5
Kingland Systems Corporation
email - justin.haase@xxxxxxxxxxxx

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Willie J. Moore
Sent: Wednesday, September 14, 2005 9:03 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Locking down an OUTQ

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



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.



CONFIDENTIALITY NOTICE:  This e-mail communication, including attachments, is 
covered by the Electronic Communications Privacy Act, 18 U.S.C. 2510-2521, is 
confidential, and may be legally privileged.  If you are not the intended 
recipient or believe you received this communication in error, please reply to 
the sender indicating that fact and delete the copy you received.  In addition, 
retention, dissemination, distribution, copying, or otherwise use of the 
information contained in this communication is strictly prohibited.  Thank you.