|
Daniel, > Hi all. When restoring a database, we lose private rights on objects. Anyone > having an idea how to solve this issue ? If it's a system bug, does a > solution come with V5R1 ? > This question is close enough to a question that I just answered on the Midrange-L that I hope you don't mind me just replaying that question and answer. If this doesn't answer your question, let me know and I'll take another shot at it. ### > I was wondering why when I save a program with private > authorities to a save file and then restore the > program to a different library I lose the private > authority. Actually, you don't lose the private authorities, they are right where they always were. :) Private authorities to an object (such as a file) are stored in the user profile object, and not in the file object. That's an important thing to understand about private authorities... So if you save a copy of file "ITEM", and then restore the file to another library, PHIL's profile still records the fact that he has *ALL authority to the original "ITEM" file. This newly restored file "ITEM" in a new library? Well User Profile PHIL has never even been told that this new file exists, so it can't be authorized to it. (This would mean that the suggested RSTAUT command would not work either) If you want object level security, then every time you introduce a new object to your system you must manage the authority to that new object. There is no "automatic security feature" that will guess what authority you want assigned to new objects, so you have to do it yourself. In this case I would recommend that after you restore the object, run the GRTOBJAUT command, and use the original "ITEM" file as a "referenced object". It's one extra step, but it will get you want you want. ### jte -- John Earl - VP & CTO The Powertech Group 253-872-7788 johnearl@powertechgroup.com www.powertechgroup.com
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.