Re: decommissioning a user

Jerry,

basically what I do is to DISABLE the user profile.  This leaves thier
structures intact but doesn't allow them to sign on to the system.  It
actually protects both of us...also, change any usrprf pw's they may have
access to...

Then do a DSPUSRPRF CANNEDPGMR for the *CMDAUT, *DEVAUT, *OBJAUT, *OBJOWN
and decide what I need to  do from there.....also I look at any security
assigned the person from any menuing or software internal assignment.

BUT, you can save yourself ALOT of work if you use generic USRPRF's for
your production objects, that way no one programmer owns production
stuff....

(I'll save the full security lecture for John or Pat  :)

Don in DC

-----------

On Thu, 16 Oct 2003, Jerry 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.
>