Re: User related Objects

>Hi everybody,
>
>If some user leaves the organization and we need to clear up the system, what
>objects should we delete?
>
>Thanks,
>Rajeev.


We have created a program that cycles through much of the work for us.  We
usually create things like user message queues and libraries with the same
name as the user profile.  This makes it easier to find them when it's time
to delete them.  The kinds of things we delete are:

System User Profile
Message queue
System Directory entry
Office/400 enrollment (this is a dwindling population...)
Shared Folders
Any library the user owns (usually only for programmers)

We also have a group of programs that cycle through all application
programs, and archive any application authoritzation to backup files.  We
also have a group of programs that allow us to retrieve a user's
authorization from the backup files, and copy it to any new profile.  This
handles those requests like, "Oh, and give him authorization to everything
that Sam, who we fired last month, could do."

Libraries and document folders are usually renamed with a "Z" in front of
them, and are not deleted.  This is in case a programmer was working on
something and left with things in progress.  Similarly, documents might be
needed after a user leaves.

Any library that begins with a "Z" is available for deletion those times
when the cry, "Oh, my God!  The Disk Is Full Again!" is heard.

--Paul E Musselman
PaulMmn@ix.netcom.com


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---