|
Chris, This is rather tangential. However if the goal is to make sure that the users associated with that group profile have access to objects created in that library may I suggest the following: 1) Create an authorization list for that library (WRKAUTL) 2) Secure that library by that authorization list GRTOBJAUT OBJ(MYLIB) OBJTYPE(*LIB) AUTL(MYAUTL) GRTOBJAUT OBJ(MYLIB) OBJTYPE(*LIB) USER(*PUBLIC) AUT(*AUTL) 3) Change the library so that all new objects use that authorization list. CHGLIB LIB(MYLIB) CRTAUT(MYAUTL) And if you make any screw up's, (Like new object was created outside of adopted authority program, etc) then at least the users will have access to it until you clean the ownership up later. And to clean the ownership up later you can always do: chgown '/QSYS.LIB/MYLIB.LIB/*' NEWOWN(MYOWNER) Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin
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.