User profile own objects not in a library

45 pts.
iseries v5r4
I have several termed user's whose user profiles contain no objects (WRKUSRPRF & Opt 12-Work With Objects Owned By User), but when I go to delete them (using Opt 4 - delete) I received the error (across the bottom of my screen) "User Profile (name) Owns Objects not In A Library".

The additional information in the message says to "Use the Reclaim Objects by Owner (RCLOBJOWN) or Reclaim Storage (RCLSTG) command to put the objects into a library."

When I do as suggested and (DSPUSRPRF TYPE(*OBJOWN)), the results are objects with a type *USRSPC.

1. In my place, what would you do and what tips & tricks would you give me to do this successfully?

2. Which command mentioned above should be used? Should it be done with all subsystems up or down?

3. How do profiles get this way? How can I prevent it in the future?

I greatly appreciate your time and attention. Thank you in advance.

Software/Hardware used:
v5r4, power system 6, 8204-E8A

Answer Wiki

Thanks. We'll let you know when a new response is added.

You can try clearing the objects from the library QRPLOBJ
IPL the server which may clear up the locks and try to delete the profiles again.

The good news is you probably don’t need to run a reclaim storage, but you may want to mention to your development staff that they should be deleting user spaces and not replacing them when they code.

Discuss This Question: 3  Replies

There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • NickHutcheson1
    Another trick, discussed a few days ago, create a default (dummy) user profile for objects that should stay on the system. When you delete the user profile, specify change object owner and point to the dummy profile. The dummy doesn't even need a password. It is kind of a catch all. I have one that I use to run jobs under with its own jobd. It just burns me up that scheduled jobs are pointed to programmers that are no longer around. I have also written programs to read through purchased software user info and delete all occurances of the profle who is gone. It simplified the task of cleanup when someone left the company.
    1,485 pointsBadges:
  • BCBGTina
    Thanks Nick, we already do something similar to your suggestion. Slack, your suggestion to clear the library might work if I could specify to only clear the *USRSPC objects. That library also has *PGM & other types of objects I don't feel comfortable deleting. I'll run your idea about deleting instead of replacing past the dev staff. Could you explain to me why or how QRPLOBJ library is used?
    45 pointsBadges:
  • TomLiotta
    If not directed by IBM, CLRLIB should not be used against any system library. For QRPLOBJ, objects might even still be in active use by user jobs in the system. Some objects might be from system jobs. Objects that you recognize can be deleted, e.g., ones you are developing. QRPLOBJ will be cleared properly at IPL. None of the objects in QRPLOBJ should get there from a RCLSTG or any other RCLxxx command. If the QRCL library shows objects after RCLxxx, you can usually recognize whether they needed to be recovered or not. If they are not needed, you can delete them. If objects are reclaimed into QRCL, it usually indicates an improper shutdown sometime in the past. It could have been from anything like a power outage, a system failure, a PWRDWNSYS while jobs are active or various other reasons. Objects that might have been in QTEMP can show up in there and are usually easy to spot and delete without concern. Others had possibly just been created, and system software didn't have time to insert pointers into the library object before ending (or some similar foul-up). The trick of creating a throwaway (dummy) user profile to hold owned objects temporarily can be very useful. Don't use QDFTOWN nor any other system profile. Tom
    125,585 pointsBadges:

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.


Share this item with your network: