Re: Listing of objects and their owners

["alan shore" <SHOREA@xxxxxxxx>]

I'll ask my second question again -
Any reason why authorization lists cannot be used?
For each library in question use the Change library command for the create 
authority paramater, for example -
CHGLIB LIB(YOURLIB)            CRTAUT(AUTHLIST)
This will ensure that any object created in that library (YOURLIB) will be 
created with the authorization lis AUTHLIB. However, any object copied form 
another library to that library will NOT.
And then create authorization lists to your hearts content.
Apply these authorization lists to each of the libraries in question,
GRTOBJAUT OBJ(your library name/*ALL) OBJTYPE(*ALL) AUTL(your authorization 
list)
then when a new user/group profile is added to the system and needs authority 
to objects within the library, the new user/group profile can be added to the 
authorization list, and automatically gain the authority to whatever the 
authority list is assigned to.


>>> <rob@dekko.com> 01/16/02 09:46AM >>>

Because the system value QCRTAUT is set to *CHANGE.  Thus if there is an
object owned by someone else, and the next user needs to delete and
recreate it they will not be able to.  Not that this should be happening a
whole lot - this is not S/36 environment - but it happens a little.


Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "alan shore"
                    <SHOREA@dime.com>         To:     <midrange-l@midrange.com>
                    Sent by:                  cc:
                    midrange-l-admin@mi       Fax to:
                    drange.com                Subject:     Re: Listing of 
objects and their owners


                    01/16/2002 09:34 AM
                    Please respond to
                    midrange-l






Again I ask, why do you need for the owner of the library to be the owner
of the objects within that library?

>>> <rob@dekko.com> 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



                    bdietz@3x.com
                    Sent by:                  To:
midrange-l@midrange.com
                    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-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.