The "feature" of OS/400 that you're missing is the fact that private authorities are not saved with an object when saving it. Here comes a bit of an OS/400 architecture lesson... the only authorities that are stored with the object are the *PUBLIC, owner's and primary group's authority. All private authorities that a user might have to an object are stored in the user's user profile object. The only time they are saved is when you are saving user profiles. So to get back the private authorities to an object, you have to restore the user profile and run the RSTAUT command. The RSTAUT command restores the private authorities, but you have to restore the profile first to build the object RSTAUT uses.
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.
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
On AS/400, the journal type AF subtype K, shows that a user profile lacks the special authority required by the function attempting to run. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.