I have a user profile that I am unable to remove from the system. The WRKOBJAUT command shows nothing. I run DSPUSRPRF *PRINT on this profile and I still see nothing listed as an owned object. Is there a way I can see what object this profile owns so that I can safely remove it.
Most likely, the profile owns Integrated File System (IFS) objects which can't be displayed using the DSPUSRPRF *OWNOBJ option or it owns internal objects that, for some reason, didn't get cleaned up properly by OS/400 and are hanging around.
To see IFS objects you either have to write to the QSYLOBJA API or you can use iSeries Navigator. Go to Users and Groups -> All Users-> right click on the user in question-> choose Delete. Before deleting you can scan for the user's owned objects. This list includes IFS objects.
If this display comes up empty, most likely it is an internal object and there is no way to display those. (These are temporary objects used in a job and are usually cleaned up by OS/400 at the end of a job.) You can either call IBM or have them look at the profile to determine if that's what the profile owns or you can take the risk and delete the profile, specifying to delete or change the ownership of the profile's owned objects.
MORE INFORMATION ON THIS TOPIC
The Best Web Links: tips, tutorials and more.
Search400's targeted search engine: Get relevant information on security.
Ask your systems management questions--or help out your peers by answering them--in our live discussion forums.
Check out this Search400.com Featured Topic: Top ten security tips
Dig Deeper on iSeries system and application security
Related Q&A from Carol Woodbury
Before changing password levels and upgrading operating systems on the AS/400, ensure the clients connecting to the NetServer do not need the old ... Continue Reading
Look in the audit journal (QAUDJRN) on the AS/400 for an authority failure message with the name of the library as the object name. Use the ... Continue Reading
When error messages arise concerning attempts to use a permanent system object without authority, find the source of the issue by looking for an AF ... Continue Reading