|
There are some things that just will not go to the group profile as a default upon creation. I'm pretty sure I had this issue with IFS objects and/or QDLS objects. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin John Myers - MM <jmyersmm@xxxxxxxxxx> Sent by: midrange-l-bounces@xxxxxxxxxxxx 10/16/2003 03:28 PM Please respond to Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> To Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx> cc Subject Re: decommissioning a user I don't know where to find such a document, but certainly ALL programmers should be set up with the objects that they create being owned by a group profile (QPGMR, for example). You can do this in their user profile. At 03:46 PM 10/16/2003, you wrote: >As people leave the company we disable their user profiles. Later we want to >delete these profiles but we need to understand object ownership, etc. >that may >be attached to a particular profile. This is even more complicated when the >user was a programmer. There are scads of instances. > >Can someone direct me to a document that outlines the general steps >necessary to >accomplish this task? Anyone have a procedure list already they would be >willing to share? > >TIA, > >Jerry _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/midrange-l or email: MIDRANGE-L-request@xxxxxxxxxxxx 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 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.