Re: our "not so" dearly departed...

["Ingvaldson, Scott" <SIngvaldson@xxxxxxxxxxxxx>]

Rick -

I solve that problem in advance, by not allowing anyone(even myself) to own
objects, using the OWNER(*GRPPRF) parameter on user profiles.  Your
applications can be secured by having a single "owner" profile (not a group
profile) that owns all of the objects in the application, so if a profile
turns up that owns objects for some reason you don't have to guess who to
change the owner to.

Scott Ingvaldson
AS/400 System Administrator
GuideOne Insurance Group
SIngvaldson@guidemail.com

-----Original Message-----
>Before removing user profiles, we have to re-assign object ownerships. I
>assume this is handled through "wrkobjown" and then by changing the objects
>to an owner that has commensurate authorities. Anything to watch out for
>with that process? All of the users will be off the system and no programs
>will be operating.
>
>Deleting objects in their personal libraries...gotta makes sure things like
>jobd's and outq's are not attached to production objects...gotta make sure
>their libraries are not embedded in some other jobd's...anything else?
>
>Thanks for your assistance everyone.
>
>Rick Rayburn