DltUsrPrf (Delete User Profile) and just in case there are any objects that she owned, you can assign them to another user or to yourself.
ANY EMPLOYEE THAT LEAVES THE COMPANY SHOULD HAVE THEIR ACCESS RIGHTS TO THE /400 AND TO ANY SERVER DELETED OR AT LEAST DISABLED AS SOON AS THEY LEAVE………ALWAYS!!!!!!!
To remove a user’s authority to an object, use the RVKOBJAUT command to revoke the authority that exists.
For example, if the user name is AUSER, and the library is MYLIB and the authority is *ALL, then run:<pre>
RVKOBJAUT OBJ( MYLIB )
OBJTYPE( *LIB )
USER( AUSER )
AUT( *ALL )</pre>
There are other methods, such as with EDTOBJAUT; but RVKOBJAUT is the direct solution.
As noted above, the first action when a user leaves employment is to set the user profile STATUS(*DISABLED) attribute. From that point, objects that were owned by that user can be deleted or transferred to other users, jobs that were scheduled by that user can be rescheduled under a different profile, and any other elements can be handle with deliberation. That process ought to be documented.