|
For example, QSYSOPR have *SPLCTL special authority to all spooled file. If I limit access outq resource authority to QSYSOPR, QSYSOPR could not operate the important spooled. I just want to limit QSYSOPR couldn't display spooled file and couldn't change outq or printer, and allow other operation for problem solving like reprint some page on some spooled file owner area locked by spoolede file woner. I can do it with VCP. Could Operation Navigater do it ? Best regards, Vengoal Chang -----Original Message----- From: midrange-l-bounces@midrange.com [mailto:midrange-l-bounces@midrange.com] On Behalf Of rob@dekko.com Sent: Tuesday, January 07, 2003 3:11 AM To: Midrange Systems Technical Discussion Subject: Re: How can I limit spooled file access under Operation NavigatorUserwith *SPLCTL special authority ? Would you have needed the VCP if you would have used AS/400 resource security? For example, if you would have done: EDTOBJAUT OBJ(MYLIB/MYOUTQ) OBJTYPE(*OUTQ) And removed access for *PUBLIC, wouldn't that be more effective? You may have to modify the CHGOUTQ OUTQ(xxxxxx) AUTCHK(???????) Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Vengoal Chang" <vengoal@ddsc.com.tw> Sent by: midrange-l-bounces@midrange.com 01/05/2003 07:43 PM Please respond to Midrange Systems Technical Discussion To: <midrange-l@midrange.com> cc: Fax to: Subject: How can I limit spooled file access under Operation Navigator User with *SPLCTL special authority ? Hi all, I used the VCP(Validity checking program) to limit user with *SPLCTL to access some important spooled file except spooled owner. How do I archive the same thing using Operation Navigator ? Best regards, Vengoal Chang _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l. _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo.cgi/midrange-l or email: MIDRANGE-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
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.