× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. January 2002

Re: Listing of objects and their owners

In order to create or move an object in/to a library, you must have *ADD
data rights to the library.  Your application may allow you to remove data
*ADD rights to your users (or certainly to most IT folks).  This would
reduce the occurrences random objects popping up in the dead of night.

jte



----- Original Message -----
From: "alan shore" <SHOREA@dime.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, January 15, 2002 11:12 AM
Subject: Re: Listing of objects and their owners


> 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.
> >>> <rob@dekko.com> 01/15/02 02:06PM >>>
>
> If an object is created on the fly, by God knows what process, what are
the
> odds that it is going to have a valid authorization list(s)?
>
> 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/15/2002 01:48 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> My question to this is
> Why do the objects in a particular library NEED to be owned by the same
> profile that owns the library?
> Any reason why authorization lists cannot be used?
>
> >>> <rob@dekko.com> 01/15/02 01:20PM >>>
>
> 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
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>                     barsa@barsaconsulti
>                     ng.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/15/2002 12:19 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
>
> I think that what you want is DSPUSRPRF TYPE(*OBJOWN), and the output file
> is QSYDSUPO.
>
> Al
>
>
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
>
>
>                     rob@dekko.com
>                     Sent by:                  To:
> midrange-l@midrange.com
>                     midrange-l-admin@mi       cc:
>                     drange.com                Subject:     Listing of
> objects and their owners
>
>
>                     01/15/02 11:06 AM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
>
> I know that I can do a DSPOBJD to an outfile and get objects, their
library
> and who owns them.  But it takes a long time to run.  And we want to run
> this on a daily basis.
>
> The file QADBIFLD list the owners, but it only contains database files.  I
> would like all objects.
>
> Is there such a file for all objects on the system?
>
> The goal is to find objects in a library owned by someone different than
> who owns the library.
>
> Rob Berendt
> --
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
> _______________________________________________
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.
>

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.