Again I ask, why do you need for the owner of the library to be the owner of the objects within that library? >>> <firstname.lastname@example.org> 01/16/02 09:30AM >>> Yes we are using groups: SSA01, SSA26, SSA30, etc. But to avoid having a ROB01, ROB26, ROB30 we add supplemental groups to ROB01 of SSA26, SSA30, etc. But the objects he creates while working with the SSA26 data will have an owner of SSA01 because that is his group profile and the owner parm is set to *GRPPRF. This parameter does not support *LIBOWN (or *PARENT, to support both libraries and directories). Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin email@example.com Sent by: To: firstname.lastname@example.org midrange-l-admin@mi cc: drange.com Fax to: Subject: Re: Listing of objects and their owners 01/16/2002 09:00 AM Please respond to midrange-l I know this thread started with you trying to find objects with the wrong owner. I am wondering if the profiles that belong to groups have the OWNER parm set to *GRPPRF. If that is set then then the group becomes the owner of created objects. I never saw any mention of the parm and was just wondering how it was set. ------------------------- Bryan Dietz 3X Corporation ======================= No, we're trying to find objects users created on the fly and now have the wrong owner. Let me explain. We have multiple divisions, 01, 26, 30, 70, etc. The file library for 01 is owned by group profile SSA01, and so on. Currently to work in either library you need multiple user profiles ROB01, ROB26, etc. Even though we negotiated with SSA to not charge for the multiple ROB's, we have some whiners here who don't like using multiple user id's. So the thought is to have ROB01 have access to all these libraries, without *ALLOBJ, by giving him supplemental groups. But if he runs something in the library owned by SSA26 then the object will be now owned by SSA01 - provided some object is created on the fly. In a better situation we would not even be using group profiles, but use program adopted authority instead - but I don't see that happening here. To use your suggestion Al, we would have to do the WRKOBJOWN for each SSA* owner and determine which are in a library that they don't belong. Rob Berendt _______________________________________________ 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/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lemail@example.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.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.